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

["Holger Hoffstätte (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153862#action_153862 ] 

Holger Hoffstätte commented on MNG-1977:
----------------------------------------

This just became a total showstopper with SpringSource effectively cloning the entire maven dependency set in their "enterprise" repo. :-(
I know that's not maven's fault, but both global exclusions (e.g. as protections again known bad poms) and aliasing (to always substitute slf4j for clogging) would really fix a lot of problems that this has caused.


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