[MENFORCER-195] Dependency convergence does not support wildcard exclusions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: 1.3.1
• Component/s: Plugin
• Environment: Maven 3.2.1
• Assignee: Robert Scholte
• Reporter: Tomaz Cerar
• Created: 09/Jun/14 10:13
• Updated: 23/Sep/20 07:12
• Resolved: 17/Jan/20 10:32

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

Issue Links

• depends upon: MSHARED-339 DependencyGraphBuilder does not provide verbose tree
• is blocked by: MSHARED-816 Annotate DependencyNodes with dependency management metadata
• is duplicated by: MENFORCER-232 DependencyConvergence doesn't acknowledge exclusion wildcards (MNG-2315)
• is duplicated by: MENFORCER-302 DependencyConvergence does not recognize exclusion wildcards
• is related to: MDEP-374 dependency:tree -Dverbose isn't verbose anymore
• requires: MNG-6713 Fix ExclusionArtifactFilter to respect wildcard
• links to: GitHub Pull Request #20
• links to: GitHub Pull Request #54
• links to: GitHub Pull Request #55
• links to: GitHub Pull Request #56