Robert Scholte created MNG-6357:
-----------------------------------
Summary: Dependency order should nearest first
Key: MNG-6357
URL: https://issues.apache.org/jira/browse/MNG-6357
Project: Maven
Issue Type: Improvement
Reporter: Robert Scholte
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
