[
https://issues.apache.org/jira/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374196#comment-15374196
]
Dariusz Kordonski commented on MENFORCER-211:
---------------------------------------------
Actually disregard my comment, our case is {{bannedDependencies}} rule, which
is different. I'll raise a separate bug.
> wildcard ignore in requireReleaseDeps
> -------------------------------------
>
> Key: MENFORCER-211
> URL: https://issues.apache.org/jira/browse/MENFORCER-211
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Affects Versions: 1.3.1
> Reporter: Arne Brix
> Priority: Minor
> Fix For: waiting-for-feedback
>
>
> the bannedDependencies rule allows one to specify artifact lists using
> wildcards:
> {code:xml}
> org.apache.*:maven-*:*
> {code}
> we are using the requireReleaseDeps rule for our release builds.
> We would like to exclude dependencies with scope test because they don't
> contribute to the final artifact.
> We tried the syntax documented for bannedDependencies, but it didn't work:
> {code:xml}
> <configuration>
> <rules>
> <requireReleaseDeps>
> <message>No Snapshots Allowed!</message>
> <onlyWhenRelease>true</onlyWhenRelease>
> <excludes>
> <exclude>*:*:*:*:test</exclude>
> </excludes>
> </requireReleaseDeps>
> </rules>
> <fail>true</fail>
> </configuration>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
