[MENFORCER-269] RequireUpperBoundDeps does not consider wildcard (*) excluded transitive dependencies

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: 1.4.1
• Component/s: Standard Rules
• Environment: maven 3.5.0
• Assignee: Robert Scholte
• Reporter: Eduard Moraru
• Created: 15/May/17 09:09
• Updated: 17/Jan/20 10:50
• Resolved: 17/Jan/20 10:33

Description

Fixing a RequireUpperBoundDeps error by using an <exclude> tag normally works, but not when the artefactId is specified with *. A crude example would be:

A
  X1 (version 1.0 but excluded for A by groupId X artefactId *)
B
  B1
    X1 (version 2.0)
C
...

The regular dependency tree properly sees this exclude and no longer lists X1 as dep of A, however, the enforcer plugin fails and still displays the excluded dependency under the "paths to dependency" trees when the error is reported.

AFAIK, wildcard excludes were introduced in MNG-3832.

Issue Links

• is related to: MNG-3832 Allow wildcards in dependency exclusions