Maven 2 & 3

merging managed dependencies happens before managed-dependency versions are interpolated

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.9, 3.0-alpha-1
  • Fix Version/s: 2.0.9, 2.1.0-M1
  • Component/s: POM
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

mergeManagedDependencies(..) happens ahead of processProjectLogic(..) inside the DefaultMavenProjectBuilder.buildInternal(..) method. This means that, if the current POM specifies an expression for one of the managed dependencies that have scope == import, the artifact resolver will fail to resolve the managed dependency with an uninterpolated version.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

fix is in place on both 2.0.x and trunk branches, but needs a unit test for completeness.

Show
John Casey added a comment - fix is in place on both 2.0.x and trunk branches, but needs a unit test for completeness.
Hide
Permalink
John Casey added a comment -

integration test is in place.

Show
John Casey added a comment - integration test is in place.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.