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 (asf.osuosl.org: domain of nicolas.deloof@capgemini.com
 designates 194.3.247.82 as permitted sender)
Message-ID: <4486C136.9030001@capgemini.fr>
Date: Wed, 07 Jun 2006 14:06:14 +0200
From: Nicolas De Loof <nicolas.deloof@capgemini.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [all] change group id? [WAS Re: [logging] RC on ibiblio ?]
References: <44337A3B.3010902@capgemini.fr> <4434BA8B.7010200@capgemini.fr>
 	<1147518485.8876.4.camel@knossos.elmet> <1147561671.5239.1.camel@blackbox>
 	<1147562491.5239.13.camel@blackbox> <446682D8.6070503@apache.org>
 	<4478CD3E.6070806@apache.org> <4478DFBB.3070206@apache.org>
 	<447D252A.2040501@apache.org> <4484A39E.9050406@apache.org>
 <98e4f1cd0606070359r31f800c1x66f7847919aeb49a@mail.gmail.com>
In-Reply-To: <98e4f1cd0606070359r31f800c1x66f7847919aeb49a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


AFAIK there is a way in maven repo to "relocate" dependencies, so that a 
POM for any commons can be published at commons-xxx groupId, that 
"relocates" to org.apache.commons" groupId.

Servletapi for example is now under "javax.servlet"
http://www.ibiblio.org/maven2/servletapi/servletapi/2.4/servletapi-2.4.pom

Using this, when maven2 search for the "latest" release of any commons 
it will look at the relocated one.

Torsten Curdt a �crit :
> Brett,
>
> any comments on this?
>
> cheers
> -- 
> Torsten
>
> On 6/6/06, Dennis Lundberg <dennisl@apache.org> wrote:
>> Brett, I did the test that you suggested.
>>
>> 1. Installed commons-lang 1.0.1 into my local repo with
>> groupId=org.apache.commons
>>
>> mvn install:install-file -DgroupId=org.apache.commons
>> -DartifactId=commons-lang -Dversion=1.0.1 -Dpackaging=jar
>> -Dfile=/path/to/commons-lang-1.0.1.jar
>>
>> 2. Created Maven 2 projects a, b and c with the dependencies mentioned
>> below.
>>
>> 3. Installed projects a and b into my local repo
>> mvn install
>>
>> 4. packaged project c as a war
>> mvn package
>>
>> The resulting war file includes both commons-lang-1.0.1.jar and
>> commons-lang-2.1.jar which was what you thought would happen.
>>
>> So this is bad, I guess. Anyone who uses commons components transitively
>> in a Maven 2 environment are likely to be bitten by this. They must keep
>> the same groupId for all commons-lang dependencies, as an example, in
>> the entire chain of transitive dependencies. I.e. they can't mix
>> groupId=commons-lang and groupId=org.apache.commons. This can be a PITA
>> since some of the dependencies are most likely out of the projects own
>> control.
>>
>> What do you suggest we do? Should we wait with this relocation until a
>> version of Maven 2 is released that can handle these kind of 
>> dependencies?
>>
>> -- 
>> Dennis Lundberg
>>
>> Brett Porter wrote:
>> > an extensive test should be something along the lines of:
>> >
>> > project A depends on commons-lang:commons-lang 2.1
>> > project B depends on o.a.c:commons-lang 1.0
>> > project C is a webapp that depends on A and B
>> >
>> > webapp should have only one commons-lang.
>> >
>> > You could do this with your own repository (and something completely
>> > artificial instead of commons-lang if it makes it easier).
>> >
>> > - Brett
>> >
>> > Dennis Lundberg wrote:
>> >> Hi Brett
>> >>
>> >> Sorry, I misunderstood you regarding when to do the testing. So, no I
>> >> haven't done the test, yet. Can you elaborate a bit more on what 
>> needs
>> >> to be tested? Perhaps you know of an artifact that has been relocated
>> >> that we can have a look at, to see how they have done.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org