You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/05/23 23:10:44 UTC

[jira] Updated: (MNG-1977) Global dependency exclusions

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

Carlos Sanchez updated MNG-1977:
--------------------------------

    Comment: was deleted

> Global dependency exclusions
> ----------------------------
>
>          Key: MNG-1977
>          URL: http://jira.codehaus.org/browse/MNG-1977
>      Project: Maven 2
>         Type: New Feature

>   Components: POM
>     Reporter: Kees de Kooter
>      Fix For: 2.1

>
>
> I depend on some libraries, which in turn depend on something
> (which in turn depend on something) that I don't want, because I declare
> some other artifact in my pom.xml.
> A concrete example: I don't want that the artifact "xerces" is imported in
> my project because I declare to depend on  "xercesImpl" which ships newer
> libraries but with the same namespaces.
> I guess I would need an "exclude transitive dependency at all", either
> globally or from this and that artifact. I saw the <exclusions> tag, but it
> forces me to be very verbose and have exact control on what is required by a
> 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