Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of nicolas.deloof@gmail.com
 designates 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=iM6a3oAnl0aNprRuslqJs07g8Ey93ujAMsux7/l3ZGd+l8jLdSaqf2yQYvxbGqyI5vvf+dKEhNgz/r8FVRxOVNPy/T2uUkBCCAhjfExZWCvxDMcsjloqqk6AQhT6LxMdvneDqJj8fwix9AQGS9EpjeA6OAsVXE3WOUeTQzC9V3k=
Message-ID: <4c39e3030702140019t53c3234ctd242c3d4fbd4b484@mail.gmail.com>
Date: Wed, 14 Feb 2007 09:19:15 +0100
From: "nicolas de loof" <nicolas.deloof@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: m2 groupIds
In-Reply-To: <F0D7281DAB048B438E8F5EC4ECEFBDDC014CFEBF@esmail.elsag.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_123837_10117716.1171441155597"
References: <F0D7281DAB048B438E8F5EC4ECEFBDDC014CFEBF@esmail.elsag.de>

------=_Part_123837_10117716.1171441155597
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 classpat=
h
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=F6rg Schaible <Joerg.Schaible@elsag-solutions.com>:
>
> 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 an=
d
> take it always into account when resolving aritfacts no matter which
> version. Scenario 1 would be completely the the enough then.
>
> - J=F6rg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

------=_Part_123837_10117716.1171441155597--