From commons-dev-return-99246-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org Wed Feb 14 09:49:34 2007 Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 14832 invoked from network); 14 Feb 2007 09:49:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2007 09:49:29 -0000 Received: (qmail 75109 invoked by uid 500); 14 Feb 2007 09:49:34 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 75034 invoked by uid 500); 14 Feb 2007 09:49:34 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 75019 invoked by uid 99); 14 Feb 2007 09:49:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2007 01:49:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [134.98.65.18] (HELO gateway.elsag.de) (134.98.65.18) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2007 01:49:24 -0800 Received: from vwall.elsag.de by gateway.elsag.de via smtpd (for herse.apache.org [140.211.11.133]) with ESMTP; Wed, 14 Feb 2007 10:49:02 +0100 Received: from esmail ([192.168.2.88]) by vwall-vs.elsag.de with InterScan Messaging Security Suite; Wed, 14 Feb 2007 10:49:01 +0100 Received: from esmail by esmail via smtpd (for vwall.elsag.de [192.168.100.108]) with ESMTP; Wed, 14 Feb 2007 10:49:01 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: m2 groupIds Date: Wed, 14 Feb 2007 10:49:01 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: m2 groupIds Thread-Index: AcdQEOGo/C/6gZ2ASX2fHB+gLNK5NAAC40OQ From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: "Jakarta Commons Developers List" X-Virus-Checked: Checked by ClamAV on apache.org nicolas de loof wrote on Wednesday, February 14, 2007 9:19 AM: > That would'nt work anyway >=20 > 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=20 > 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. Yep. You're right. Another missing gap. If the new POM contains some = information, that it had been relocated from a different place, Maven = could take it into account. Currently Maven knows about the relocation = only, if you try to download an uncached version from the repo with the = old groupId. If the dep is referenced with the new groupId already, = Maven is as blind as reading old POMs from the cache. I fear switching the groupId for commons will create some real = disruptions :-/ - J=F6rg --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org