Should be possible to add a mojo to the maven-dependency-plugin to scan for duplicate classes in scope XYZ... that would be the major indicator.
Of course you'd need include/excludes... and ignores... and failure mode control.... probably want a report as well... can you file a JIRA for it... if nobody has implemented it by xmas, I'll take a bite -Stephen 2009/12/9 Jörg Schaible <joerg.schai...@gmx.de> > Hi Brian, > > Brian Fox wrote at Mittwoch, 9. Dezember 2009 04:44: > > > No but when projects move group or artifactIds, they are supposed to > > create a pom with relocation info in it, then Maven is able to mediate > > the conflicts. > > Apart from relocation, Mirko's idea is quite interesting in case some > artifacts have been used that collect other packages without knowing. > Prominent example has been cglib-2.x (containing the ASM 1.5.x stuff that > broke Hibernate 3.0 using ASM 2.x) or stuff like groovy-all. I know quite > some more innocent-looking artifacts that may break other dependencies > because of "class bundling". > > Also relocation cannot work if an artifact is splitted (avalon-framework). > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
