[mojo-dev] [jira] (MOJO-2059) BanDuplicateClasses fails the build when two versions of an artifact are in the dependency tree

[Curtis Rueden (JIRA)]

Title: Message Title

Curtis Rueden created an issue   Mojo / MOJO-2059 BanDuplicateClasses fails the build when two versions of an artifact are in the dependency tree Issue Type: Bug Affects Versions: extra-enforcer-rules-1.0-beta-3 Assignee: Unassigned Attachments: seuss.zip Components: extra-enforcer-rules Created: 11/Dec/14 2:02 PM Priority: Major Reporter: Curtis Rueden When a project's dependency tree includes multiple versions of the same artifact (i.e., the same GA with different Vs), the banDuplicateClasses rule fails the buildâ€?e.g.: [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanDuplicateClasses failed with message: No Duplicate Classes Allowed! Found in: org.slf4j:slf4j-api:jar:1.7.6:compile org.slf4j:slf4j-api:jar:1.7.2:compile Duplicate classes: org/slf4j/helpers/BasicMarker.class There may be others but <findAllDuplicates> was set to false, so failing fast The bug is caused by the use of DependencyNode#getArtifact() instead of getRelatedArtifact(), here: https://fisheye.codehaus.org/browse/~tag=extra-enforcer-rules-1.0-beta-3/mojo/tags/extra-enforcer-rules-1.0-beta-3/src/main/java/org/apache/maven/plugins/enforcer/AbstractResolveDependencies.java?hb=true#to125 And probably also here: https://fisheye.codehaus.org/browse/~tag=extra-enforcer-rules-1.0-beta-3/mojo/tags/extra-enforcer-rules-1.0-beta-3/src/main/java/org/apache/maven/plugins/enforcer/AbstractResolveDependencies.java?hb=true#to103 Using getRelatedArtifact() instead resolves the artifacts to the version chosen by Maven's conflict resolution, avoiding this issue. Add Comment   This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email