Maven 2 & 3

Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.11, 2.2.1, 3.0-beta-3
  • Fix Version/s: 3.0
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

If some code triggers dependency resolution for an artifact in the reactor when that project artifact hasn't been built yet and the resolution reaches out to a remote repo instead, any later resolution attempts will stick to the artifact from the repo even if the reactor produced the artifact in the meantime.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MSITE-495 project.getDependencyArtifacts() returns null under forked multimodule report execution

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

A demo project which exhibits the issue upon running mvn org.apache.maven.plugins:maven-javadoc-plugin:2.7:aggregate package -X. Here, the javadoc plugin will cause dependency resolution for the entire reactor (before anyhing has been actually built) and resolves the producer artifact from the remote repo. When performing the package lifecycle next, the classpaths of consumer still use the producer artifact from the local repo instead from the now populated reactor.

Show
Benjamin Bentmann added a comment - A demo project which exhibits the issue upon running mvn org.apache.maven.plugins:maven-javadoc-plugin:2.7:aggregate package -X . Here, the javadoc plugin will cause dependency resolution for the entire reactor (before anyhing has been actually built) and resolves the producer artifact from the remote repo. When performing the package lifecycle next, the classpaths of consumer still use the producer artifact from the local repo instead from the now populated reactor.
Hide
Permalink
Benjamin Bentmann added a comment -

Fixed in r997938.

Show
Benjamin Bentmann added a comment - Fixed in r997938 .

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Benjamin Bentmann
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: