You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2014/12/07 20:02:10 UTC

[jira] (MENFORCER-211) wildcard ignore in requireReleaseDeps

    [ https://jira.codehaus.org/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358761#comment-358761 ] 

Karl-Heinz Marbaise commented on MENFORCER-211:
-----------------------------------------------

Can you describe more in detail what you mean by ", but it didn't work" ? 

> wildcard ignore in requireReleaseDeps
> -------------------------------------
>
>                 Key: MENFORCER-211
>                 URL: https://jira.codehaus.org/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.1.6#6162)