Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.0.9
-
Component/s: Dependencies
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
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
-
MNGECLIPSE-476
dependencies should not be sorted but in the order of pom
-
-
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
-
-
MNG-4263
Dependencies resolution & the order in the declaration
-
-
MNG-2541
Dependecy order is lost
-
-
MNG-3197
Direct dependencies should come before transitive dependencies in build classpath.
-
- is related to
-
MNG-3111
Classpath order incorrect
-
-
MNG-3494
local pom dependencies should get injected before inherited dependencies
-
-
MECLIPSE-152
Write .classpath with ordered dependencies [incl. Patch]
-
- relates to
-
MECLIPSE-388
Correct classpath ordering in .classpath
-
-
MANTTASKS-22
artifact:dependencies does not respect in the generated classpath the order of the dependencies
-
-
MANTTASKS-91
[task dependencies]Trouble between mvn and manttasks
-
-
MNG-3473
site generation with 2.0.9 and plugin:report (2.4 ONLY) is broken
-
-
MNG-3805
Ordering of extension class path is indeterministic
-
-
MNG-3813
[regression] Plugin class path does not respect ordering of plugin dependencies
-
-
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
-
Is there a reason for this order or it's only a "cosmetic" reason? AFAIK unless you have the same classes in multiple dependencies the order has no effect.