maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eduard Moraru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MENFORCER-269) RequireUpperBoundDeps does not consider wildcard (*) excluded transitive dependencies
Date Mon, 15 May 2017 09:09:04 GMT
Eduard Moraru created MENFORCER-269:
---------------------------------------

             Summary: RequireUpperBoundDeps does not consider wildcard (*) excluded transitive
dependencies
                 Key: MENFORCER-269
                 URL: https://issues.apache.org/jira/browse/MENFORCER-269
             Project: Maven Enforcer Plugin
          Issue Type: Improvement
          Components: Standard Rules
    Affects Versions: 1.4.1
         Environment: maven 3.5.0
            Reporter: Eduard Moraru


Fixing a {{RequireUpperBoundDeps}} error by using an {{<exclude>}} tag normally works,
but not when the {{artefactId}} is specified with {{*}}. A crude example would be:
{noformat}
A
  X1 (version 1.0 but excluded for A by groupId X artefactId *)
B
  B1
    X1 (version 2.0)
C
...
{noformat}

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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message