[MNG-6357] Dependency order should be nearest first

• Type: Improvement
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 4.0.x-candidate
• Assignee: Unassigned
• Reporter: Robert Scholte
• Created: 07/Feb/18 20:00
• Updated: 28/Jul/23 15:23

Description

In case of version conflicts, the nearest wins. However, the dependency order is simply based on tree walking. In the rare that a transitive dependency of the first direct dependency contains the same class as a latter direct dependency, the code is compiled against the first one, which is odd.

It would make more sense if direct dependencies are the first ones on the classpath, followed by the first level transitive dependencies, etc. This will make the explanation equal to version conflict resolution: nearest wins.

I don't expect real issues due to this change, otherwise we would have had this issue much earlier. This should become the new default order, however there should be a system property to get the original order, just in case somebody needs it.

 

Current workaround: make the critical dependency the first direct dependency.

Issue Links

• is related to: MCOMPILER-317 Plugin generates wrong modulepath (dependencies listed in wrong order)
• is superceded by: MNG-7852 Use all the versions for dependency resolution rather than "nearest first" or "declared first"
• links to: GitHub Pull Request #47
• links to: GitHub Pull Request #281