[
https://jira.codehaus.org/browse/MENFORCER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280371#comment-280371
]
Vincent Massol commented on MENFORCER-83:
-----------------------------------------
I have the exact same need. I've had to develop a custom enforcer rule that
extends BannedDependencies, see
https://github.com/xwiki/xwiki-commons/blob/73c8404f08ba36136d08c48bbacc9b88f04a07e6/xwiki-commons-tools/xwiki-commons-tool-enforcer-dependencies/src/main/java/org/xwiki/tool/enforcer/XWikiBannedDependencies.java
Thanks!
> Banned dependencies should support regular expressions
> ------------------------------------------------------
>
> Key: MENFORCER-83
> URL: https://jira.codehaus.org/browse/MENFORCER-83
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 1.0-beta-1
> Reporter: Eric Lewis
>
> The includes and excludes of the bannedDependencies rule support wildcards,
> but only for an entire section.
> They should be enhanced to support regular expressions.
> For instance instead of having
> <includes>
> <include>my.company:abc-api</include>
> <include>my.company:def-api</include>
> <include>my.company:ghi-api</include>
> <include>my.company:jkl-api</include>
> </includes>
> one would specify
> <includes>
> <include>my.company:.*\-api</include>
> </includes>
> To be compatible, the wildcard '*' would be treated as regular expression '.*'
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
