Maven Shared Components

Mediate dependency versions for stricter Maven3 ProjectSorter

Details

  • Number of attachments :
    0

Description

We currently depend on maven-project:2.0.8, but with Maven3 about to be released we should upgrade our dependencies to 3.0. In Maven3, maven-project has been moved into maven-core:3.0.

Maven3 also brings in changes to ProjectSorter via MNG-3814. This means that versions are considered when ordering dependencies. This affects maven-runtime as only the mediated version of a dependency is available at runtime and thus vertices of the runtime dependency graph can be neglected, leading to incorrect ordering from MavenRuntime.getSortedProjects.

To resolve this we need to inject the runtime version of all discovered artifacts into the parsed MavenProjects prior to sorting. This will emulate the situation that we have at runtime.

Issue Links

depends upon

Improvement - An improvement or enhancement to an existing feature or task. MSHARED-227 Upgrade dependencies to Maven3

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

Bug - A problem which impairs or prevents the functions of the product. MNG-3814 Reactor builds fail due to erroneous cycle in project sorting which does not consider versions

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

Activity

Hide
Permalink
Mark Hobson added a comment -

Set all project dependency versions to the corresponding version discovered at runtime now that Maven3's ProjectSorter considers versions.

Show
Mark Hobson added a comment - Set all project dependency versions to the corresponding version discovered at runtime now that Maven3's ProjectSorter considers versions.

People

  • Assignee:
    Mark Hobson
    Reporter:
    Mark Hobson
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: