[ http://jira.codehaus.org/browse/MNG-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101446 ]
Joerg Schaible commented on MNG-3090: ------------------------------------- This might also be correlated to an issue I reported on the list just before M207 was released: http://article.gmane.org/gmane.comp.jakarta.turbine.maven.devel/79492 Since I could not reproduce it with a stripped down project, I did not open a separate JIRA issue. However, this issue is the show-stopper for us using M207. I can confirm that Christian's test case works with M205 and fails for me with M206 + M207. > 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: http://jira.codehaus.org/browse/MNG-3090 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories > Affects Versions: 2.0.7 > Reporter: Christian Schulte > Attachments: maven-artifact-2.0.x.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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira