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

["Robert Scholte (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MENFORCER-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MENFORCER-269.
------------------------------------
      Assignee: Robert Scholte
    Resolution: Done

integration tests added in [588f2750d41e4ecbfbb5252ce2729605339cf248|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=588f2750d41e4ecbfbb5252ce2729605339cf248]
Required change is in Maven 3.6.3!

> 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
>            Assignee: Robert Scholte
>            Priority: Major
>
> 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
(v8.3.4#803005)