[
http://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261031#action_261031
]
Rob Elliot commented on MNG-1977:
---------------------------------
Could this not be achieved via a new scope? I'm thinking:
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.1.1</version>
<scope>excluded</scope>
</dependency>
Semantics would be that any artifactId declared in this way would be guaranteed
not to be on either the test or main runtime or compile time classpath, and
neither would any of its transitive dependencies, and its transitive
dependencies would not be added to the declaring pom's transitive dependencies,
regardless of version number or where in the transitive dependency tree it
occurred.
> 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
>
>
> 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
