You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/05/24 20:23:04 UTC

[jira] Updated: (MNG-1797) Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

     [ http://jira.codehaus.org/browse/MNG-1797?page=all ]

John Casey updated MNG-1797:
----------------------------

    Fix Version:     (was: 2.0.5)

> 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
>         Type: Bug

>     Versions: 2.0.1
>     Reporter: David Hawkins
>  Attachments: MNG-1797-maven-project.patch, MNG-1797-unit-test.patch, it1019.tgz, it1020.tgz
>
>
> 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