Uploaded image for project: 'Maven Enforcer Plugin'
  1. Maven Enforcer Plugin
  2. MENFORCER-269

RequireUpperBoundDeps does not consider wildcard (*) excluded transitive dependencies

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.4.1
    • Fix Version/s: None
    • Component/s: Standard Rules
    • Labels:
      None
    • Environment:
      maven 3.5.0

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rfscholte Robert Scholte
                Reporter:
                enygma Eduard Moraru
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: