[
http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178253#action_178253
]
Pierre-Antoine Grégoire commented on MNG-1977:
----------------------------------------------
It's a sad thing that this will never be available for backports because the
pom model cannot be changed..
This is a very much awaited feature. And though I like a lot tools of the like
of Nexus (Artifactory is also very nice BTW), I think Maven should provide
these mechanisms and that maybe 2.1 release was a bit rushed in this prospect.
Is there a timeframe for 3.0 already?
Why is this not planned for 2.2 for example?
> 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.x
>
>
> 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
