[
http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154004#action_154004
]
Brian Fox commented on MNG-1977:
--------------------------------
That's a lovely development. If you use Nexus, you can control which artifacts
come from a given repo so you can prevent the springsource repo from polluting
your team. There's nothing that can be done inside maven for global exclusions
until 3.0 since it requires a model change in the pom.
> 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
