[ https://jira.codehaus.org/browse/MENFORCER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356039#comment-356039 ]
Grégory Joseph commented on MENFORCER-168: ------------------------------------------ @Karl I'm facing the same problem and was about to report it as well with a sample project. I guess Conny is using {{validate}} the same way I do - validate that my poms are correct. It seems a fair assumption that enforcer rules can be applied in these cases. Just because the artifact don't exist yet doesn't mean we can't build a dependency tree. (OTOH I just tried {{mvn dependency:tree}} on my test project and it fails the same way, so if anything, that's maybe something that would need to be fixed in Maven itself, and that'd have a whole lot of other implications ... ? > In a multi module project "bannedDependencies" rule tries to resolve project > artifacts from external repository > --------------------------------------------------------------------------------------------------------------- > > Key: MENFORCER-168 > URL: https://jira.codehaus.org/browse/MENFORCER-168 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Standard Rules > Affects Versions: 1.3.1 > Reporter: Conny Kreyssel > Priority: Critical > > I have created a pull request with a IT case on github. > see https://github.com/apache/maven-enforcer/pull/6 > Seems to be a problem with maven 3.1.1. The IT runs with maven 3.0.4 but > fails with 3.1.1. -- This message was sent by Atlassian JIRA (v6.1.6#6162)