[
http://jira.codehaus.org/browse/MENFORCER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier closed MENFORCER-72.
------------------------------
Resolution: Fixed
Fix Version/s: 1.0-beta-2
Assignee: Paul Gier
Fixed in [r989917|http://svn.apache.org/viewvc?view=revision&revision=989917].
> Add scope to bannedDependencies rule
> ------------------------------------
>
> Key: MENFORCER-72
> URL: http://jira.codehaus.org/browse/MENFORCER-72
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 1.0-beta-1
> Reporter: Baptiste MATHUS
> Assignee: Paul Gier
> Priority: Minor
> Fix For: 1.0-beta-2
>
>
> It would be fine if this enforcer rule could be tuned more finely to fail
> only if some dependency is put with some specified scope (the same could be
> done for the optional tag, btw).
> In fact, in my case, I'd like to be sure that no project of ours is using
> log4j as a compile dependency, but it is allowed as a runtime one.
> Another example: no project should ever have servlet-api as a dependency,
> with another scope than provided.
> Thanks in advance.
> Cheers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
