[ http://jira.codehaus.org/browse/MNG-1797?page=all ]
John Casey closed MNG-1797.
---------------------------
Assignee: John Casey
Resolution: Fixed
Fix Version/s: (was: 2.1)
2.0.5
Applied the code patch, but I added a simpler unit test.
> Dependency excludes apply to every subsequent dependency, not just the one it
> is declared under.
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-1797
> URL: http://jira.codehaus.org/browse/MNG-1797
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: David Hawkins
> Assigned To: John Casey
> Fix For: 2.0.5
>
> Attachments: it1019.tgz, it1020.tgz, MNG-1797-maven-project.patch,
> MNG-1797-unit-test.patch
>
>
> If you specify ANY dependency excludes, all dependencies after that one in
> the pom will also exclude what you specified. They appear to be cumulative
> on every dependency in that they bleed over into sibling dependencies.
> It's easy to test if you add an exclusion to a random dependency. This
> exclusion should exclude a required transitive dependency that is included by
> a dependency lower in the list. You will find that the dependency lower in
> the list no longer includes the required dependency because it is using the
> filter you declared in the other dependency.
--
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
