Return-Path: 
 <commons-dev-return-93284-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 94293 invoked from network); 4 Sep 2006 22:06:07 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 4 Sep 2006 22:06:07 -0000
Received: (qmail 25455 invoked by uid 500); 4 Sep 2006 22:06:05 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 25096 invoked by uid 500); 4 Sep 2006 22:06:04 -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 25085 invoked by uid 99); 4 Sep 2006 22:06:04 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2006 15:06:04 -0700
X-ASF-Spam-Status: No, hits=2.1 required=10.0
	tests=DATE_IN_FUTURE_24_48
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [82.209.166.4] (HELO smtp.bredband2.net) (82.209.166.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2006 15:06:03 -0700
Received: (qmail 2938 invoked from network); 4 Sep 2006 21:59:21 -0000
Received: from me-179-122-233-83.3.cust.bredband2.com (HELO [192.168.0.100])
 ([83.233.122.179])
          (envelope-sender <dennisl@apache.org>)
          by smtp.bredband2.net (qmail-ldap-1.03) with SMTP
          for <commons-dev@jakarta.apache.org>; 4 Sep 2006 21:59:21 -0000
Message-ID: <44FF462C.6070401@apache.org>
Date: Thu, 07 Sep 2006 00:05:32 +0200
From: Dennis Lundberg <dennisl@apache.org>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: VOTE: Migrate commons-fileupload to Maven 2
References: <44F88777.3020502@gmail.com>
	 <8a81b4af0609012257i25de4c8dx1a5b816196022ed1@mail.gmail.com>
 <f8b39ace0609012313s7591ac88lafd1226d9239bde6@mail.gmail.com>
In-Reply-To: <f8b39ace0609012313s7591ac88lafd1226d9239bde6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Craig McClanahan wrote:
> On 9/1/06, Phil Steitz <phil.steitz@gmail.com> wrote:
>>
>> <snip>
>> We also need to definitively settle the artifact naming conventions
>> and think carefully about the impact of relocating the fileupload jar.
> 
> 
> 
> I *think* the following strategy will deal with this situation ... and
> should generic to all the commons packages:
> 
> * If version x.y.z of Commons package "foo" is published as Maven artifact
>  "commons-foo:commons-foo:x.y.z", publish an *additional* copy of that
>  same version under "org.apache.commons.foo:commons-foo:x.y.z".
> 
> * For all future versions, use only the"org.apache.commons" group id.
> 
> That way, we won't disrupt current Maven-based users of the current
> versions, and we also don't have to wait until each individual package revs
> to publish versions under the new id.  Users who are updating their 
> projects
> to depend on a new version number can easily update the group id at the 
> same
> time.
> 
> Does that make any sense?
> 
> 
> Phil
> 
> 
> 
> Craig
> 

I've documented the procedure for doing this here:

   http://maven.apache.org/guides/mini/guide-relocation.html

-- 
Dennis Lundberg

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