[ 
https://issues.apache.org/jira/browse/MENFORCER-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MENFORCER-195:
-------------------------------------
    Description: 
Maven 3.2 introduced wildcard exclusions for dependencies.

But if you use them dependencyConvergence wrongly complains about conflicting 
transitive dependencies.

*WORKAROUND Maven 3.6.2:* Start the exclusion-list with the explicit groupID 
and artifactId, ending with the exclusions containing wildcards. This will 
restore the behavior as before MNG-6713

  was:
Maven 3.2 introduced wildcard exclusions for dependencies.

But if you use them dependencyConvergence wrongly complains about conflicting 
transitive dependencies.

*WORKAROUND:* Start the exclusion-list with the explicit groupID and 
artifactId, ending with the exclusions containing wildcards. This will restore 
the behavior as before MNG-6713


> Dependency convergence does not support wildcard exclusions
> -----------------------------------------------------------
>
>                 Key: MENFORCER-195
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-195
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Plugin
>    Affects Versions: 1.3.1
>         Environment: Maven 3.2.1
>            Reporter: Tomaz Cerar
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Maven 3.2 introduced wildcard exclusions for dependencies.
> But if you use them dependencyConvergence wrongly complains about conflicting 
> transitive dependencies.
> *WORKAROUND Maven 3.6.2:* Start the exclusion-list with the explicit groupID 
> and artifactId, ending with the exclusions containing wildcards. This will 
> restore the behavior as before MNG-6713



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to