You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/07/24 12:30:00 UTC
[jira] [Closed] (MENFORCER-211) wildcard ignore in
requireReleaseDeps
[ https://issues.apache.org/jira/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MENFORCER-211.
------------------------------------
Fix Version/s: (was: waiting-for-feedback)
3.0.0
Assignee: Robert Scholte
Resolution: Fixed
Fixed in [5409be83dc3b621121e6222ad3830f8e95cf6614|https://gitbox.apache.org/repos/asf?p=maven-enforcer.git;a=commit;h=5409be83dc3b621121e6222ad3830f8e95cf6614]
Documentation has been updated to explain what the pattern looks like.
> 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
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 3.0.0
>
>
> 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
(v8.3.4#803005)