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