You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2020/01/17 10:33:00 UTC
[jira] [Closed] (MENFORCER-195) Dependency convergence does not
support wildcard exclusions
[ https://issues.apache.org/jira/browse/MENFORCER-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MENFORCER-195.
------------------------------------
Assignee: Robert Scholte
Resolution: Done
integration tests added in [588f2750d41e4ecbfbb5252ce2729605339cf248|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=588f2750d41e4ecbfbb5252ce2729605339cf248]
Required change is in Maven 3.6.3!
> 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
> Assignee: Robert Scholte
> Priority: Major
> Time Spent: 1h 20m
> 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.4#803005)