maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MNG-6357) Dependency order should be nearest first
Date Wed, 07 Feb 2018 20:01:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte updated MNG-6357:
--------------------------------
    Summary: Dependency order should be nearest first   (was: Dependency order should nearest
first )

> Dependency order should be nearest first 
> -----------------------------------------
>
>                 Key: MNG-6357
>                 URL: https://issues.apache.org/jira/browse/MNG-6357
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Robert Scholte
>            Priority: Major
>
> 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)

Mime
View raw message