[
http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114464
]
Wolfgang Nagele commented on MNG-1977:
--------------------------------------
I can just agree to others here, this is indeed a VERY important feature. It
would ease the development a lot. As if you currently have such a bogus
dependency you'll have to copy and paste every possible exclusion to every
dependency. This is really ugly and costs a lot of time.
> 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: 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
