[mojo-dev] [jira] (MOJO-2077) BanDuplicateClasses finds duplicates with things that aren't in dependency tree

[Ryan Gardner (JIRA)]

Title: Message Title

Ryan Gardner created an issue   Mojo / MOJO-2077 BanDuplicateClasses finds duplicates with things that aren't in dependency tree Issue Type: Bug Affects Versions: extra-enforcer-rules-1.0-beta-3 Assignee: Unassigned Attachments: updateDuplicateClassDependencyResolver1.patch Components: extra-enforcer-rules Created: 30/Mar/15 9:39 AM Priority: Major Reporter: Ryan Gardner The AbstractResolveDependencies seems to use an older dependency tree resolver - so it doesn't properly exclude things that are excluded by * excludes. I looked at the way the enforcer-rules do it now, and basically copied their "check I included a zip that has an example of a project that fails with duplicate class errors against 1.0-beta3 but shouldn't. I also updated the "mojo-1682" integration test - because that test was specifically enforcing a scenario that doesn't exist in maven 3. (It was specifying two versions of the same artifact and expecting duplicate classes to be caught) All other tests pass unchanged and the new IT that I include fails with before applying the changes to the AbstractResolveDependencies, but passes after making those changes. 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