[MNG-1412] dependency sorting in classpath

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.0.9
• Component/s: Dependencies
• Assignee: Herve Boutemy
• Reporter: Mark Hobson
• Created: 03/Nov/05 11:23
• Updated: 08/Feb/20 15:41
• Resolved: 03/Feb/08 05:33

Description

The .classpath file entries should be ordered by nearest transitiveness (if that's a word).

For example, I have project A that depends on B that depends on C. The classpath for A is generated in the order C, B. Ideally the classpath should be in order of how near they are to the project, i.e. B, C.

Issue Links

• is depended upon by: MDEP-150 Indeterministic artifact ordering can cause bogus warnings
• is duplicated by: MNG-2914 order of elements in ClassPathElement is not as in pom.xml
• is duplicated by: MNG-4263 Dependencies resolution & the order in the declaration
• is duplicated by: MNG-2541 Dependecy order is lost
• is duplicated by: MNG-3197 Direct dependencies should come before transitive dependencies in build classpath.
• is related to: MNG-3111 Classpath order incorrect
• is related to: MNG-3494 local pom dependencies should get injected before inherited dependencies
• is related to: MECLIPSE-152 Write .classpath with ordered dependencies [incl. Patch]
• relates to: MECLIPSE-388 Correct classpath ordering in .classpath
• relates to: MANTTASKS-22 artifact:dependencies does not respect in the generated classpath the order of the dependencies
• relates to: MANTTASKS-91 [task dependencies]Trouble between mvn and manttasks
• relates to: MNG-3473 site generation with 2.0.9 and plugin:report (2.4 ONLY) is broken
• relates to: MNG-3805 Ordering of extension class path is indeterministic
• relates to: MNG-3813 [regression] Plugin class path does not respect ordering of plugin dependencies
• relates to: MNG-4026 [regression] Order of project class path does not match POM order during reactor build
• supercedes: MNG-2258 Wrong execution order of plugins in same phase