That would'nt work anyway If you allready downloaded commons-cc:1.1 and get (maybe transitiviely) a dependency on org.apache.commons:cc:1.2, you will get both in your classpath as maven will not kwon those tow groupIds are for the same artifact.
We can't expect maven to reload the 1.1 POM that is allready present in local repository (an other cache/mirror/proxy) We could only expect maven to know from the 1.2 POM that what the old groupId was to establish the two artifacts are same. This requires some changes in the POM format to include a section about artifact "history" in maven repo. Nico. 2007/2/14, Jörg Schaible <[EMAIL PROTECTED]>:
Hi Carlos, Carlos Sanchez wrote on Wednesday, February 14, 2007 8:25 AM: > right a relocate pom for ALL versions is required to avoid > duplication on classpath BUT as I said almost everybody will have > cached previous versions of commons so they won't see the relocation > until they delete local repo and the poms with relocation info get > downloaded. Maven should give here better support. If it ever downloads a relocation POM it should keep the relocation information in a separate DB/storage and take it always into account when resolving aritfacts no matter which version. Scenario 1 would be completely the the enough then. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
