[
https://issues.apache.org/jira/browse/MENFORCER-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920182#comment-16920182
]
Falko Modler commented on MENFORCER-195:
----------------------------------------
I am not entirely sure whether the following issue is related with this ticket
but I do guess so:
With Maven 3.6.1 and Enforcer Plugin 3.0.0-M2, wildcard-exclusions for
artifactId _do work for me_.
But with the soon to be released Maven 3.6.2
(https://lists.apache.org/thread.html/b892c3a9a4250dcc439f80e9b44b9c01b8e4edf5317d175a2e1cb7cc@%3Cdev.maven.apache.org%3E),
DependencyConvergence fails, as if it doesn't properly evaluate the the
exclusions anymore.
dependency:tree is identical to 3.6.1, though...
PS, scenario: I have a few transitive dependencies bringing in an old version
of javassist which I need to override with a newer one.
> 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.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
