[ https://issues.apache.org/jira/browse/MDEP-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790937#comment-14790937 ]
Kristian Rosenvold commented on MDEP-490: ----------------------------------------- Please stop name dropping people to catch their attention. In a lot of cases it has the opposite intention of what you want. > Add flag to analyze-dep-mgt goal to ignore exclusion errors > ----------------------------------------------------------- > > Key: MDEP-490 > URL: https://issues.apache.org/jira/browse/MDEP-490 > Project: Maven Dependency Plugin > Issue Type: Improvement > Reporter: Jonathan Haber > > I would like to run the analyze-dep-mgt goal with failBuild=true, but it > doesn't work because of exclusion errors. One common example is libraries > that accidentally depend on junit at compile scope instead of test scope. > When I encounter a library like this, I add an exclusion on junit. But I have > junit in my dependency tree at test scope, so my build fails with a message > like: > {quote} > [INFO] junit:junit:jar was excluded in DepMgt, but version 4.11 has been > found in the dependency tree. > {quote} > I think the simplest fix is to add a flag to the analyze-dep-mgt goal to > ignore exclusion errors. I just want to use the goal to check for version > mismatches, if I want to enforce banned dependencies the > maven-enforcer-plugin has more robust support for this. I implemented this > change in [this|https://github.com/apache/maven-plugins/pull/54] pull > request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)