[
https://jira.codehaus.org/browse/MENFORCER-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347747#comment-347747
]
Paul Gier commented on MENFORCER-195:
-------------------------------------
I wasn't able to reproduce a build failure. I experimented with enforcer 1.3,
1.3.1, and the latest 2.0-SNAPSHOT. Using Maven 3.1 and lower I saw the
following warnings:
{noformat}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.maven.its.enforcer:ban-transitive-test:jar:1.0
[WARNING] 'dependencies.dependency.exclusions.exclusion.groupId' for
org.apache.myfaces.core:myfaces-impl:jar with value '*' does not match a valid
id pattern. @ line 51, column 20
[WARNING] 'dependencies.dependency.exclusions.exclusion.artifactId' for
org.apache.myfaces.core:myfaces-impl:jar with value '*' does not match a valid
id pattern. @ line 52, column 23
[WARNING]
{noformat}
But the dependencies appeared to be excluded, and the build was successful.
Using Maven 3.2.1, there were no warnings, and the dependencies were excluded
as expected.
> Ban bad depedencies does not support wildcard exclusions
> --------------------------------------------------------
>
> Key: MENFORCER-195
> URL: https://jira.codehaus.org/browse/MENFORCER-195
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.3.1
> Environment: Maven 3.2.1
> Reporter: Tomaz Cerar
>
> Maven 3.2 introduced wildcard exclusions for dependencies.
> But if you use them ban-bad-dependencies wrongly complains that transitive
> dependencies are still present.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
