You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@maven.org> on 2006/12/09 20:16:37 UTC

A single groupId for Maven?

Hi,

Just looking at our proliferation of projects and that we have many  
groupIds and I'm wondering if we should be doing that and encouraging  
that?

Should all our projects here have a groupId of org.apache.maven?

Jason.

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


Re: A single groupId for Maven?

Posted by Jason van Zyl <ja...@maven.org>.
On 10 Dec 06, at 7:23 PM 10 Dec 06, Brett Porter wrote:

> I would recommend projects use subgroups for logical groupings of  
> modules.
>

Well that's exactly what to decide. Even amongst our own projects  
we're not consistent.

Upside to logical groupings are that it's tidier (as Andy says) in  
the repository, the downside is that you cannot cleanly grab/analyze  
the output from one group like org.apache.maven without doing some  
calculations which might be simple.

Anyone else have any thoughts?

Jason.

> On 11/12/2006, at 11:15 AM, Jason van Zyl wrote:
>
>> On 10 Dec 06, at 7:05 PM 10 Dec 06, Brett Porter wrote:
>>
>>> I agree with Jesse. Apart from the occasional inconsistency, I  
>>> think what we have now is fine.
>>>
>>
>> Occasional inconsistency or are we the only project that does it?  
>> I'm not sure what we're doing is something we should be promoting  
>> as a best practice. In Plexus we have a single groupId and I  
>> haven't looked at the Spring project to see what they are doing  
>> but we should be trying to encourage some convention here.
>>
>> Jason.
>>
>>> - Brett
>>>
>>> On 10/12/2006, at 11:13 AM, Jesse McConnell wrote:
>>>
>>>> personally I like the nesting of a particular project under the
>>>> groupId, like org.apache.maven.continuum...
>>>>
>>>> just unfortunate that maven was..well maven since
>>>> org.apache.maven.maven would look rather goofy and its a bit  
>>>> late to
>>>> change that :)
>>>>
>>>> what did you have in mind jason?  pull things like continuum down a
>>>> notch group wise and fill up the org.apache.maven group space with
>>>> lots and lots of artifacts across all subprojects?
>>>>
>>>> jesse
>>>>
>>>> On 12/9/06, Eric Redmond <er...@gmail.com> wrote:
>>>>> If projects like Wagon and SCM will always be managed by the  
>>>>> Maven project,
>>>>> then it makes sense to put them under org.apache.maven. If they  
>>>>> are planned
>>>>> to eventuall become stand-alone projects, used outside of  
>>>>> maven, it kind of
>>>>> makes more sense to me to keep the groupIds distinct as they  
>>>>> are - if
>>>>> something like SCM will eventually be like "org.apache.scm"  
>>>>> anyway.
>>>>>
>>>>> Which leads me to ask: what is a group, exactly? Is it a  
>>>>> (probably rotating)
>>>>> team of developers? Or a specific project? If the former, I'd  
>>>>> say make them
>>>>> org.apache.maven. If the latter, keep them as is.
>>>>>
>>>>> Thanks;
>>>>> Eric
>>>>>
>>>>> On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
>>>>> >
>>>>> > Hi,
>>>>> >
>>>>> > Just looking at our proliferation of projects and that we  
>>>>> have many
>>>>> > groupIds and I'm wondering if we should be doing that and  
>>>>> encouraging
>>>>> > that?
>>>>> >
>>>>> > Should all our projects here have a groupId of org.apache.maven?
>>>>> >
>>>>> > Jason.
>>>>> >
>>>>> >  
>>>>> ------------------------------------------------------------------ 
>>>>> ---
>>>>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> > For additional commands, e-mail: dev-help@maven.apache.org
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>> --
>>>>> Eric Redmond
>>>>> http://codehaus.org/~eredmond
>>>>>
>>>>>
>>>>
>>>>
>>>> -- 
>>>> jesse mcconnell
>>>> jesse.mcconnell@gmail.com
>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


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


Re: A single groupId for Maven?

Posted by Brett Porter <br...@apache.org>.
I would recommend projects use subgroups for logical groupings of  
modules.

On 11/12/2006, at 11:15 AM, Jason van Zyl wrote:

> On 10 Dec 06, at 7:05 PM 10 Dec 06, Brett Porter wrote:
>
>> I agree with Jesse. Apart from the occasional inconsistency, I  
>> think what we have now is fine.
>>
>
> Occasional inconsistency or are we the only project that does it?  
> I'm not sure what we're doing is something we should be promoting  
> as a best practice. In Plexus we have a single groupId and I  
> haven't looked at the Spring project to see what they are doing but  
> we should be trying to encourage some convention here.
>
> Jason.
>
>> - Brett
>>
>> On 10/12/2006, at 11:13 AM, Jesse McConnell wrote:
>>
>>> personally I like the nesting of a particular project under the
>>> groupId, like org.apache.maven.continuum...
>>>
>>> just unfortunate that maven was..well maven since
>>> org.apache.maven.maven would look rather goofy and its a bit late to
>>> change that :)
>>>
>>> what did you have in mind jason?  pull things like continuum down a
>>> notch group wise and fill up the org.apache.maven group space with
>>> lots and lots of artifacts across all subprojects?
>>>
>>> jesse
>>>
>>> On 12/9/06, Eric Redmond <er...@gmail.com> wrote:
>>>> If projects like Wagon and SCM will always be managed by the  
>>>> Maven project,
>>>> then it makes sense to put them under org.apache.maven. If they  
>>>> are planned
>>>> to eventuall become stand-alone projects, used outside of maven,  
>>>> it kind of
>>>> makes more sense to me to keep the groupIds distinct as they are  
>>>> - if
>>>> something like SCM will eventually be like "org.apache.scm" anyway.
>>>>
>>>> Which leads me to ask: what is a group, exactly? Is it a  
>>>> (probably rotating)
>>>> team of developers? Or a specific project? If the former, I'd  
>>>> say make them
>>>> org.apache.maven. If the latter, keep them as is.
>>>>
>>>> Thanks;
>>>> Eric
>>>>
>>>> On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
>>>> >
>>>> > Hi,
>>>> >
>>>> > Just looking at our proliferation of projects and that we have  
>>>> many
>>>> > groupIds and I'm wondering if we should be doing that and  
>>>> encouraging
>>>> > that?
>>>> >
>>>> > Should all our projects here have a groupId of org.apache.maven?
>>>> >
>>>> > Jason.
>>>> >
>>>> >  
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> > For additional commands, e-mail: dev-help@maven.apache.org
>>>> >
>>>> >
>>>>
>>>>
>>>> --
>>>> Eric Redmond
>>>> http://codehaus.org/~eredmond
>>>>
>>>>
>>>
>>>
>>> -- 
>>> jesse mcconnell
>>> jesse.mcconnell@gmail.com
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

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


Re: A single groupId for Maven?

Posted by Jason van Zyl <ja...@maven.org>.
On 10 Dec 06, at 7:05 PM 10 Dec 06, Brett Porter wrote:

> I agree with Jesse. Apart from the occasional inconsistency, I  
> think what we have now is fine.
>

Occasional inconsistency or are we the only project that does it? I'm  
not sure what we're doing is something we should be promoting as a  
best practice. In Plexus we have a single groupId and I haven't  
looked at the Spring project to see what they are doing but we should  
be trying to encourage some convention here.

Jason.

> - Brett
>
> On 10/12/2006, at 11:13 AM, Jesse McConnell wrote:
>
>> personally I like the nesting of a particular project under the
>> groupId, like org.apache.maven.continuum...
>>
>> just unfortunate that maven was..well maven since
>> org.apache.maven.maven would look rather goofy and its a bit late to
>> change that :)
>>
>> what did you have in mind jason?  pull things like continuum down a
>> notch group wise and fill up the org.apache.maven group space with
>> lots and lots of artifacts across all subprojects?
>>
>> jesse
>>
>> On 12/9/06, Eric Redmond <er...@gmail.com> wrote:
>>> If projects like Wagon and SCM will always be managed by the  
>>> Maven project,
>>> then it makes sense to put them under org.apache.maven. If they  
>>> are planned
>>> to eventuall become stand-alone projects, used outside of maven,  
>>> it kind of
>>> makes more sense to me to keep the groupIds distinct as they are  
>>> - if
>>> something like SCM will eventually be like "org.apache.scm" anyway.
>>>
>>> Which leads me to ask: what is a group, exactly? Is it a  
>>> (probably rotating)
>>> team of developers? Or a specific project? If the former, I'd say  
>>> make them
>>> org.apache.maven. If the latter, keep them as is.
>>>
>>> Thanks;
>>> Eric
>>>
>>> On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
>>> >
>>> > Hi,
>>> >
>>> > Just looking at our proliferation of projects and that we have  
>>> many
>>> > groupIds and I'm wondering if we should be doing that and  
>>> encouraging
>>> > that?
>>> >
>>> > Should all our projects here have a groupId of org.apache.maven?
>>> >
>>> > Jason.
>>> >
>>> >  
>>> -------------------------------------------------------------------- 
>>> -
>>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> > For additional commands, e-mail: dev-help@maven.apache.org
>>> >
>>> >
>>>
>>>
>>> --
>>> Eric Redmond
>>> http://codehaus.org/~eredmond
>>>
>>>
>>
>>
>> -- 
>> jesse mcconnell
>> jesse.mcconnell@gmail.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


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


Re: A single groupId for Maven?

Posted by Brett Porter <br...@apache.org>.
I agree with Jesse. Apart from the occasional inconsistency, I think  
what we have now is fine.

- Brett

On 10/12/2006, at 11:13 AM, Jesse McConnell wrote:

> personally I like the nesting of a particular project under the
> groupId, like org.apache.maven.continuum...
>
> just unfortunate that maven was..well maven since
> org.apache.maven.maven would look rather goofy and its a bit late to
> change that :)
>
> what did you have in mind jason?  pull things like continuum down a
> notch group wise and fill up the org.apache.maven group space with
> lots and lots of artifacts across all subprojects?
>
> jesse
>
> On 12/9/06, Eric Redmond <er...@gmail.com> wrote:
>> If projects like Wagon and SCM will always be managed by the Maven  
>> project,
>> then it makes sense to put them under org.apache.maven. If they  
>> are planned
>> to eventuall become stand-alone projects, used outside of maven,  
>> it kind of
>> makes more sense to me to keep the groupIds distinct as they are - if
>> something like SCM will eventually be like "org.apache.scm" anyway.
>>
>> Which leads me to ask: what is a group, exactly? Is it a (probably  
>> rotating)
>> team of developers? Or a specific project? If the former, I'd say  
>> make them
>> org.apache.maven. If the latter, keep them as is.
>>
>> Thanks;
>> Eric
>>
>> On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
>> >
>> > Hi,
>> >
>> > Just looking at our proliferation of projects and that we have many
>> > groupIds and I'm wondering if we should be doing that and  
>> encouraging
>> > that?
>> >
>> > Should all our projects here have a groupId of org.apache.maven?
>> >
>> > Jason.
>> >
>> >  
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>>
>>
>> --
>> Eric Redmond
>> http://codehaus.org/~eredmond
>>
>>
>
>
> -- 
> jesse mcconnell
> jesse.mcconnell@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

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


Re: A single groupId for Maven?

Posted by Jesse McConnell <je...@gmail.com>.
personally I like the nesting of a particular project under the
groupId, like org.apache.maven.continuum...

just unfortunate that maven was..well maven since
org.apache.maven.maven would look rather goofy and its a bit late to
change that :)

what did you have in mind jason?  pull things like continuum down a
notch group wise and fill up the org.apache.maven group space with
lots and lots of artifacts across all subprojects?

jesse

On 12/9/06, Eric Redmond <er...@gmail.com> wrote:
> If projects like Wagon and SCM will always be managed by the Maven project,
> then it makes sense to put them under org.apache.maven. If they are planned
> to eventuall become stand-alone projects, used outside of maven, it kind of
> makes more sense to me to keep the groupIds distinct as they are - if
> something like SCM will eventually be like "org.apache.scm" anyway.
>
> Which leads me to ask: what is a group, exactly? Is it a (probably rotating)
> team of developers? Or a specific project? If the former, I'd say make them
> org.apache.maven. If the latter, keep them as is.
>
> Thanks;
> Eric
>
> On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
> >
> > Hi,
> >
> > Just looking at our proliferation of projects and that we have many
> > groupIds and I'm wondering if we should be doing that and encouraging
> > that?
> >
> > Should all our projects here have a groupId of org.apache.maven?
> >
> > Jason.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> Eric Redmond
> http://codehaus.org/~eredmond
>
>


-- 
jesse mcconnell
jesse.mcconnell@gmail.com

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


Re: A single groupId for Maven?

Posted by Eric Redmond <er...@gmail.com>.
If projects like Wagon and SCM will always be managed by the Maven project,
then it makes sense to put them under org.apache.maven. If they are planned
to eventuall become stand-alone projects, used outside of maven, it kind of
makes more sense to me to keep the groupIds distinct as they are - if
something like SCM will eventually be like "org.apache.scm" anyway.

Which leads me to ask: what is a group, exactly? Is it a (probably rotating)
team of developers? Or a specific project? If the former, I'd say make them
org.apache.maven. If the latter, keep them as is.

Thanks;
Eric

On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
>
> Hi,
>
> Just looking at our proliferation of projects and that we have many
> groupIds and I'm wondering if we should be doing that and encouraging
> that?
>
> Should all our projects here have a groupId of org.apache.maven?
>
> Jason.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
Eric Redmond
http://codehaus.org/~eredmond

Re: A single groupId for Maven?

Posted by Mike Perham <mp...@gmail.com>.
I think the groupIds should all start with that but we should have
some sort of reasonable best practice for tiers beneath that.  For
instance, "org.apache.maven.plugins" makes perfect sense for me.  Or
is that what you are suggesting?

On 12/9/06, Jason van Zyl <ja...@maven.org> wrote:
> Hi,
>
> Just looking at our proliferation of projects and that we have many
> groupIds and I'm wondering if we should be doing that and encouraging
> that?
>
> Should all our projects here have a groupId of org.apache.maven?
>

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