You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Samuel Langlois (JIRA)" <ji...@codehaus.org> on 2012/06/08 12:37:23 UTC
[jira] (MNG-2315) Add option to exclude all transitive dependencies
for a particular one
[ https://jira.codehaus.org/browse/MNG-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300608#comment-300608 ]
Samuel Langlois commented on MNG-2315:
--------------------------------------
Like the 134 other people who voted for it, I'd love to see this implemented.
There are quite a few bad poms in Central, especially for old artifacts, and they will be here forever.
In case you haven't seen it on MNG-3832, a workaround is to use wildcard on exclusion:
{code}
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
{code}
It works in Maven 3, although it produces a nasty warning about threatened build stability and support in future versions.
I guess the fix could simply be to remove this warning... :-)
> Add option to exclude all transitive dependencies for a particular one
> ----------------------------------------------------------------------
>
> Key: MNG-2315
> URL: https://jira.codehaus.org/browse/MNG-2315
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Carlos Sanchez
> Priority: Critical
> Fix For: 3.1
>
>
> Something like
> <dependency>
> ...
> <excludeTransitive>true</excludeTransitive>
> </dependency>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira