[
https://jira.codehaus.org/browse/MOJO-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MOJO-1799.
--------------------------------
Resolution: Fixed
Fix Version/s: extra-enforcer-rules-1.0-alpha-3
Assignee: Robert Scholte
Fixed in [rev. 15703|http://fisheye.codehaus.org/changelog/mojo/?cs=15703]
> Add configuration option to define which dependency scopes to include in the
> check
> ----------------------------------------------------------------------------------
>
> Key: MOJO-1799
> URL: https://jira.codehaus.org/browse/MOJO-1799
> Project: Mojo
> Issue Type: New Feature
> Components: extra-enforcer-rules
> Affects Versions: extra-enforcer-rules-1.0-alpha-2
> Reporter: Mirko Nasato
> Assignee: Robert Scholte
> Fix For: extra-enforcer-rules-1.0-alpha-3
>
>
> I would like to exclude test dependencies from the banDuplicateClasses check,
> I'm only interested in what ends up in the WEB-INF/lib classpath of my webapp.
> I actually wrote a similar plugin before discovering this one that's already
> in the central maven repo; I don't want to duplicate efforts but I miss scope
> configurability. Feel free to take any useful code from
> https://github.com/mirkonasato/maven-dependency-sanity-plugin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
