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

People

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

Dates

  • Created:
    Updated:
    Resolved: