[
http://jira.codehaus.org/browse/MNG-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260646#action_260646
]
Alex Alvarez edited comment on MNG-3832 at 3/18/11 3:38 AM:
------------------------------------------------------------
I have given up all hope, MNG-2315 which is similar has been lying there since
2006.
If tit helps anyone, the most widespread workaround that I have seen is to
import the offending jar to the local maven repository under another name.
was (Author: alex.alvarez):
I have given up all hope, MNG-2315 which is similar has been lying there
since 2006.
> Allow wildcards in dependency exclusions
> ----------------------------------------
>
> Key: MNG-3832
> URL: http://jira.codehaus.org/browse/MNG-3832
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
> Reporter: Paul Gier
> Fix For: 3.1
>
> Attachments: MNG-3832-maven-artifact.patch
>
>
> I would like to be able to exclude all transitive dependencies from a certain
> dependencies. This is especially useful when depending on an artifact with a
> classifier that may not have the same dependencies as the main artifact.
> Currently the only way to do this is by excluding each dependency
> individually which requires significant effort and is prone to becoming out
> of date. The following syntax is one possibility.
> Exclude all transitive dependencies
> {code}
> <exclusion>
> <groupId>*</groupId>
> </exclusion>
> {code}
> Exclude transitive dependencies with the groupId "org.company"
> {code}
> <exclusion>
> <groupId>org.company</groupId>
> <artifactId>*</artifactId>
> </exclusion>
> {code}
--
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
