[
http://jira.codehaus.org/browse/MNG-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198237#action_198237
]
Tomek Bujok commented on MNG-3832:
----------------------------------
The solution I have implemented could be easily included to 2.2.2 version. Many
people urgently require this feature (There are 16 votes here and 74 in
MNG-2315) Is the approach that I implemented inline with the Maven2
architecture? I can implement it once more or correct the patch in order to
have this ticket resolved in 2.2.2 version.
> Allow wildcards in dependency exclusions
> ----------------------------------------
>
> Key: MNG-3832
> URL: http://jira.codehaus.org/browse/MNG-3832
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Reporter: Paul Gier
> Fix For: 2.x
>
> 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
