[MECLIPSE-711] .classpath generated does not consider inter-dependency order and is generally alphabetically ordered

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Auto Closed
• Affects Version/s: 2.8
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Environment: mvn 3.0.3, windows xp
• Assignee: Unassigned
• Reporter: Leon Chadwick
• Created: 26/Jan/12 11:56
• Updated: 06/Sep/15 20:44
• Resolved: 06/Sep/15 20:44

Description

Looking at EclipseClasspathWriter.java, it generally relies on config.getDepsOrdered() to return the classpath entries in the correct order.
The Comparator for that ordering is alphabetical.

This means if I have modules that must come earlier in the list of classpath entries (lets say because we are overriding a classname from another module) then it is just a matter of luck whether this will build based upon the alphabetical order of these two modules. The order should instead consider that if a module has a depdendency on another module it should come first in the classpath.

I see that IdeDepdendency class is passed a dependencyDepth in constructor but this is not used, perhaps that should be part of the comparator in getDepsOrdered() ?

I marked this as a blocker, as if you have a project that needs to build, with this issue it won't, and I can't.