Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Done
-
1.3.1
-
None
-
None
-
Maven 3.2.1
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
Attachments
Issue Links
- depends upon
-
MSHARED-339 DependencyGraphBuilder does not provide verbose tree
- Closed
- is blocked by
-
MSHARED-816 Annotate DependencyNodes with dependency management metadata
- Closed
- is duplicated by
-
MENFORCER-232 DependencyConvergence doesn't acknowledge exclusion wildcards (MNG-2315)
- Closed
-
MENFORCER-302 DependencyConvergence does not recognize exclusion wildcards
- Closed
- is related to
-
MDEP-374 dependency:tree -Dverbose isn't verbose anymore
- Closed
- requires
-
MNG-6713 Fix ExclusionArtifactFilter to respect wildcard
- Closed
- links to