You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by sebb <se...@gmail.com> on 2010/05/21 16:40:44 UTC
[Nexus] Starting to use Nexus in Commons
In Commons we are want to try using Nexus for the next release of
Commons Compress.
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?
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!]
S///
Re: [Nexus] Starting to use Nexus in Commons
Posted by sebb <se...@gmail.com>.
On 24/05/2010, Brian Fox <br...@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 <se...@gmail.com> wrote:
> > On 24/05/2010, Brian Demers <bd...@sonatype.com> wrote:
> >>
> >> On Fri, May 21, 2010 at 10:40 AM, sebb <se...@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///
> >> >
> >>
> >>
> >
>
Re: [Nexus] Starting to use Nexus in Commons
Posted by Brian Fox <br...@sonatype.com>.
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.
On Mon, May 24, 2010 at 10:38 AM, sebb <se...@gmail.com> wrote:
> On 24/05/2010, Brian Demers <bd...@sonatype.com> wrote:
>>
>> On Fri, May 21, 2010 at 10:40 AM, sebb <se...@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///
>> >
>>
>>
>
Re: [Nexus] Starting to use Nexus in Commons
Posted by sebb <se...@gmail.com>.
On 24/05/2010, Brian Demers <bd...@sonatype.com> wrote:
>
> On Fri, May 21, 2010 at 10:40 AM, sebb <se...@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///
> >
>
>
Re: [Nexus] Starting to use Nexus in Commons
Posted by Brian Demers <bd...@sonatype.com>.
On Fri, May 21, 2010 at 10:40 AM, sebb <se...@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.
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?
If not we would set up the permissions so someone from commons-collections
didn't accidentally change/promote any staged artifacts for
commons-compress.
>
> 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///
>