Return-Path: 
 <commons-dev-return-90173-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 95248 invoked from network); 14 Jun 2006 19:35:16 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 14 Jun 2006 19:35:16 -0000
Received: (qmail 75533 invoked by uid 500); 14 Jun 2006 19:35:12 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 75511 invoked by uid 500); 14 Jun 2006 19:35:12 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 75500 invoked by uid 99); 14 Jun 2006 19:35:12 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 12:35:12 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of niall.pemberton@gmail.com
 designates 64.233.184.229 as permitted sender)
Received: from [64.233.184.229] (HELO wr-out-0506.google.com) (64.233.184.229)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 12:35:12 -0700
Received: by wr-out-0506.google.com with SMTP id i2so116650wra
        for <commons-dev@jakarta.apache.org>;
 Wed, 14 Jun 2006 12:34:51 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=PI/Q2Z9z3FXSvW9KT/IMHbm8Q9Px9cxnlqPJ3sxdzivMhRMjVuHAWryZb8UA4JmP/XWhyB/cq5tgiXGznnsMOUw6RAdRWHIXgITpzuqZ1y9G8WJne/2QJz4Rx4JtRRsRoIRQLZSbC+yx7W6d9BjqTuWdtRjjkGYXfkMItB3moX0=
Received: by 10.54.142.18 with SMTP id p18mr930639wrd;
        Wed, 14 Jun 2006 12:34:51 -0700 (PDT)
Received: by 10.54.158.3 with HTTP; Wed, 14 Jun 2006 12:34:51 -0700 (PDT)
Message-ID: <55afdc850606141234l5407969ak884da72aca9829e3@mail.gmail.com>
Date: Wed, 14 Jun 2006 20:34:51 +0100
From: "Niall Pemberton" <niall.pemberton@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [all] change group id? [WAS Re: [logging] RC on ibiblio ?]
In-Reply-To: <4484A39E.9050406@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Whats the state of play with this - I was just about to do the release
for Chain 1.1 - it has been modified to have
<groupId>org.apache.commons</groupId> - is it OK to release with this
or should I revert to <groupId>commons-chain</groupId>?

Niall

On 6/5/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
>
>

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