[
http://jira.codehaus.org/browse/MENFORCER-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox closed MENFORCER-73.
------------------------------
Resolution: Fixed
Fix Version/s: 1.0-beta-2
I updated the error message to suggest the use of dependency:tree. Embedding
the tree function inside a rule is a major undertaking that I think would
introduce more problems than it solves.
> Display dependency "path" when bannedDependencies rule fails
> ------------------------------------------------------------
>
> Key: MENFORCER-73
> URL: http://jira.codehaus.org/browse/MENFORCER-73
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 1.0-beta-1
> Reporter: Baptiste MATHUS
> Priority: Minor
> Fix For: 1.0-beta-2
>
>
> At the moment, when bannedDependencies rule is violated, something like the
> following is printed:
> {quote} [WARNING] Rule 2:
> org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
> Found Banned Dependency: commons-logging:commons-logging:jar:1.1.1{quote}
> I guess it would be great if this rule could print the same output than
> dependency:tree -Dincludes=the-specified-artifact/group. It would give
> something like:
> {quote} [WARNING] Rule 2:
> org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
> Found Banned Dependency: commons-logging:commons-logging:jar:1.1.1 :
> somegroupId:someArtifactId:jar:1.0.2
> +- someotherone...
> +- commons-logging...
> {quote}
> 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
