You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/29 02:09:58 UTC

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

     [ http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-1977:
-------------------------------

    Fix Version/s:     (was: 3.x)
                   3.1.alpha1

> Global dependency exclusions
> ----------------------------
>
>                 Key: MNG-1977
>                 URL: http://jira.codehaus.org/browse/MNG-1977
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>          Components: POM
>            Reporter: Kees de Kooter
>             Fix For: 3.1.alpha1
>
>
> 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