[MSHARED-165] Mediate dependency versions for stricter Maven3 ProjectSorter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-runtime-1.0-alpha-1
• Fix Version/s: maven-runtime-1.0-alpha-3
• Component/s: maven-runtime (RETIRED)
• Assignee: Mark Hobson
• Reporter: Mark Hobson
• Created: 06/Oct/10 05:00
• Updated: 08/Feb/20 15:41
• Resolved: 22/May/12 06:39

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: MSHARED-227 Upgrade dependencies to Maven3
• is related to: MNG-3814 Reactor builds fail due to erroneous cycle in project sorting which does not consider versions