[ 
https://jira.codehaus.org/browse/MNG-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326011#comment-326011
 ] 

Matt Yates commented on MNG-3832:
---------------------------------

This gentleman (Jos Dirksen) figured out what's going on and describes it [on 
his blog|http://www.smartjava.org/content/maven-and-wildcard-exclusions]
In short, the above discussed {{ExcludesArtifactFilter}} is not even called (at 
least in Maven 3)
Exclusions checks are instead made by 
[ExclusionDependencySelector|https://github.com/sonatype/sonatype-aether/blob/master/aether-util/src/main/java/org/sonatype/aether/util/graph/selector/ExclusionDependencySelector.java]
 which handles the wildcard cases
Basically, the only thing the needs to happen now is clean up of the warnings 
you get when you try to do this
                
> Allow wildcards in dependency exclusions
> ----------------------------------------
>
>                 Key: MNG-3832
>                 URL: https://jira.codehaus.org/browse/MNG-3832
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>          Components: Dependencies
>            Reporter: Paul Gier
>             Fix For: 3.2
>
>         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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to