Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 72.14.220.158 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=GY5AN8sw6fjQLEcrMt+/b5u8lnVoKZIITrmMdLNEY5KV4rC+RBdnz8LcVkks9xxakf
         PjzI3ehxNOZAGRKZy+Kml/Xnk84ZS+PlxCJ674pMVeF7eKSWJUdqBXAHXoxisSFoaKPb
         o3+IZ+ffk1eo8C4L5GyLhEw68wgP3K4pSMN9A=
MIME-Version: 1.0
In-Reply-To: <AANLkTimTESvrmYTfKc68e7eXOCtPU-ykeqBckPGvv7Ie@mail.gmail.com>
References: <AANLkTimdByzqH3LjY4_lXhswlaJzTSuz39wdjRgnODPk@mail.gmail.com>
	 <AANLkTinrj5_FGXdKYh34ryJwYpZUzXF3NW9Y7v1lVBCj@mail.gmail.com>
	 <AANLkTikzCxQp5Zl17AoZ4ay0a1w5NZAK0a1pqNCoWmfe@mail.gmail.com>
	 <AANLkTimTESvrmYTfKc68e7eXOCtPU-ykeqBckPGvv7Ie@mail.gmail.com>
Date: Mon, 24 May 2010 22:03:46 +0100
Message-ID: <AANLkTiklVAaH493ZaJMTyjF_r_eczbIlAtgLfmtyvIyE@mail.gmail.com>
Subject: Re: [Nexus] Starting to use Nexus in Commons
From: sebb <sebbaz@gmail.com>
To: repository@apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 24/05/2010, Brian Fox <brianf@sonatype.com> wrote:
> Sebb,
>  Regardless of Nexus, the commons projects are supposed to be moving
>  towards org.apache based groupIds. My understanding is that each
>  project was going to do this on the next major release to minimize
>  churn.
>
>  It is true that currently only org.apache.* projects are using Nexus
>  at this time. It's not a limitation of the system, rather noone has
>  asked.
>

OK, thanks!

>  On Mon, May 24, 2010 at 10:38 AM, sebb <sebbaz@gmail.com> wrote:
>  > On 24/05/2010, Brian Demers <bdemers@sonatype.com> wrote:
>  >>
>  >> On Fri, May 21, 2010 at 10:40 AM, sebb <sebbaz@gmail.com> wrote:
>  >> > In Commons we are want to try using Nexus for the next release of
>  >> > Commons Compress.
>  >> >
>  >>
>  >> Great!
>  >> >
>  >> > Some questions have been raised about using Nexus for all of Commons,
>  >> > since not all of Commons components have a groupid of
>  >> > "org.apache.commons", and changing groupid may not be feasible for
>  >> > some.
>  >> >
>  >> > Can Nexus be used for other groupids?
>  >> >
>  >>
>  >> Yes, the only thing we need to know is what the access control should be.
>  >
>  > I only see org/apache under
>  > https://repository.apache.org/content/repositories/snapshots/
>  >
>  > So is it just chance that only groupIds starting with org.apache
>  > currently use Nexus?
>  >
>  >> Do all the commons developers have access to all the org.apahce.commons
>  >> projects?  Do the other commons projects share the same list of commiters?
>  >
>  > At present all commons committers have access to all commons SVN code,
>  > but most committers only work on a few components.
>  >
>  >> If not we would set up the permissions so someone from commons-collections
>  >> didn't accidentally change/promote any staged artifacts for
>  >> commons-compress.
>  >
>  > I need to confirm the permssion scheme with Commons.
>  >
>  > Does Nexus use LDAP groups for the permissions?
>  >
>  >> >
>  >> > Also, if we start using Nexus for a particular component, do we have
>  >> > to continue using it? Or can we revert to the old way for one or more
>  >> > releases?
>  >> > [I expect people will want to stick with Nexus - once they have tried it!]
>  >> >
>  >> >
>  >> Nothing holds a project to use Nexus.
>  >>
>  >> > S///
>  >> >
>  >>
>  >>
>  >
>