Return-Path: 
 <commons-dev-return-92706-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 73830 invoked from network); 15 Aug 2006 18:43:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 15 Aug 2006 18:43:50 -0000
Received: (qmail 86725 invoked by uid 500); 15 Aug 2006 18:43:48 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 86653 invoked by uid 500); 15 Aug 2006 18:43:48 -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 86640 invoked by uid 99); 15 Aug 2006 18:43:48 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 11:43:48 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of rahul.akolkar@gmail.com
 designates 64.233.166.179 as permitted sender)
Received: from [64.233.166.179] (HELO py-out-1112.google.com) (64.233.166.179)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 11:43:47 -0700
Received: by py-out-1112.google.com with SMTP id x31so664642pye
        for <commons-dev@jakarta.apache.org>;
 Tue, 15 Aug 2006 11:43:27 -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=gksy7vJD4bV9cPpvhRu6goCajV27Y16hhlTFX7JPd5DjFbC/TnIEzm32v0hklBI6juAaOpbvRYZVmeZjIxOYziQq8tvmufeZkE4NMdWCnN/NxpbCJ1WIdS+BzNmwhECBehlV9F2TbFATHzH3CQ4Ifwn3qlLQLRI25XoduS1osT8=
Received: by 10.35.20.14 with SMTP id x14mr16101721pyi;
        Tue, 15 Aug 2006 11:43:27 -0700 (PDT)
Received: by 10.35.68.5 with HTTP; Tue, 15 Aug 2006 11:43:26 -0700 (PDT)
Message-ID: <ce1f2ea80608151143i42e076b4q318bc655b72f2e17@mail.gmail.com>
Date: Tue, 15 Aug 2006 14:43:26 -0400
From: "Rahul Akolkar" <rahul.akolkar@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [all] maven group ids
In-Reply-To: <44DDFC81.9010905@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44DDFA41.30503@oliver-heger.de> <44DDFC81.9010905@apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 8/12/06, Dennis Lundberg <dennisl@apache.org> wrote:
> Oliver Heger wrote:
> > Hi,
> >
> > just wanted to ask if there is already a resolution related to the
> > groupIds of commons components.
> >
<snip/>
>
> Everything is set to make the transition to the new groupId. I was
> hoping that we could use the upcoming release of configuration as the
> first release with the new groupId.
>
<snap/>

Do we want to do this? Shouldn't we transition all of Commons together
(as Tomasz implies in previous post, and just like we did with the
JIRA transition). Suboptimal if folks have to look up which components
have migrated yet, there are different groupIds for Commons components
in the same POM etc.

Now, the relocation guide below (thanks for that!) talks about
resigning POMs etc., which basically means we need everyone who has
signed a Commons release (POM) to participate here?

-Rahul


> I will do the necessary work to relocate this and previous releases of
> configuration, once the release has been made, so that the transition is
> as transparent as possible to downstream users. More info on what steps
> need to be taken can be found 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