[
https://jira.codehaus.org/browse/MENFORCER-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329776#comment-329776
]
Robert Scholte commented on MENFORCER-162:
------------------------------------------
As weird as it may sound, but it is actually a extra-enforcer-rule issue. It
expects that all dependencies are already resolved, which is an invalid
assumption. There are more extra-enforcer-rules which have this kind of
problems, I've already started to fix it there.
I'll leave this issue open until the extra-enforcer-rules are fixed, because
I'm pretty sure more users will blame the maven-enforcer-plugin.
> maven-enforcer-plugin 1.3.1 no longer fails when duplicate classes are found
> ----------------------------------------------------------------------------
>
> Key: MENFORCER-162
> URL: https://jira.codehaus.org/browse/MENFORCER-162
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Reporter: David Boden
> Priority: Critical
>
> I'll provide more details if this proves difficult to recreate. For now, I
> just wanted to log my observation that 1.3.1 does not find duplicate classes
> on the classpath whereas 1.3 does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
