Is not eassier. I've discovered that transitive dependencies is a maven 2 feature, with maven 1 that is not possible. This is a project of about 200 people, we can't change that.
-----Mensaje original----- De: Antonio Petrelli [mailto:[email protected]] Enviado el: martes, 31 de agosto de 2010 12:12 Para: Maven Users List Asunto: Re: using 2 or more different version of an artifact in a single pom 2010/8/31 Grau Aracil, Manuel <[email protected]>: > Is a dependency from a dependency. Suppose our project uses artifact XXX-1.0, > and, a jar from our project uses XXX-1.1. If they are binary-compatible, then I suggest to choose one (the most recent one, I suppose) and exclude the other. If they are not, well, welcome to jar hell :-D In fact, Maven is protecting you from a potential problem: same classes in different jars, that *will* cripple your classloader. It's not a Maven problem, but a Java feature. In this case, the best approach is to migrate your project to use 1.1 version of that dependency. You might use the Shade plugin to get a version of a library with modified package names: http://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html But, in your case, I think that migration is easier... or not? Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
