[
https://jira.codehaus.org/browse/MNG-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-3090:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Nearest dependency, which is not included by a filter, wins, although a
> farthest dependency, which is included by the same filter, does not win.
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3090
> URL: https://jira.codehaus.org/browse/MNG-3090
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.7
> Reporter: Christian Schulte
> Assignee: Jason van Zyl
> Attachments: maven-artifact-2.0.x.patch, MNG-3090.patch,
> testcase.tar.bz2
>
>
> There seems to be a problem with transitive dependencies and the nearest wins
> strategy. The nearest dependency wins, although a filter is in use which will
> not include that dependency when there is the same dependency at a deeper
> level, where it is included by the same filter. The nearest dependency gets
> discarded (e.g. is missing on the compile classpath) although the farthest
> dependency would have been included. Please see the comments in the attached
> patch.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
