hello, Oh yes of course, that is correct. it will add "multiple copies of the JAR with the same instead of different packages". From this POV it makes sense to enforce new package names.
the wiki page helps to make that clear. Would be good to have a replacement meta entry in the maven repo which is actually observed by the resolver for such cases. greetings Bernd -- http://bernd.eckenfels.net ----- Ursprüngliche Nachricht ----- Von: "sebb" <seb...@gmail.com> Gesendet: 29.07.2014 08:03 An: "Commons Developers List" <dev@commons.apache.org> Betreff: Re: [bcel] BCEL 6.0 review On 29 July 2014 01:59, Bernd Eckenfels <e...@zusammenkunft.net> wrote: > Am Mon, 28 Jul 2014 19:34:05 +0100 > schrieb sebb <seb...@gmail.com>: > >> There must be a 1-1 correspondance between the Maven pair {group id, >> artifact id} and package name. >> Otherwise Maven can add multiple copies of the jar to the same >> classpath. Jar hell. > > Uh, why is that? > > I think the maven version resolving is soley based on > coordinates. If you have different versions of a given coordinate it > will chose one. If you rename it, it will use both - no matter if it > has same package as others or not. Exactly. So Maven needs to be told (via the coords) which jars have the same packages and which are different. See https://wiki.apache.org/commons/MavenAndClasspath which is my attempt to explain this further. > I think only the OSGi/bnd stuff looks at the packages. And the Java classloader. > Gruss > Bernd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
