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: [email protected] For additional commands, e-mail: [email protected]
