Re: best practices of naming WAS: svn commit: r349270

[Brett Porter <br...@apache.org>]

I just wanted to capture what I thought we were doing currently (albeit
inconsistently). I'm happy to discuss.

I certainly see your points below, but I think there are also good cases
for separation (eg Jorg was asking about excalibur, and it made sense to
me for all the components to have their own group, just like maven
plugins and maven archetypes).

Others?

- Brett

Vincent Massol wrote:
> 
>> -----Original Message-----
>> From: brett@apache.org [mailto:brett@apache.org]
>> Sent: dimanche 27 novembre 2005 19:09
>> To: commits@maven.apache.org
>> Subject: svn commit: r349270 -
>> /maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt
> 
> [snip]
> 
>> + * A good way to determine the granularity of the group ID is to use the
>> project structure. That is, if
>> + the current project is a multiple module project, it should append a new
>> identifier to the parent's
>> + group ID.
>> +
>> + eg. <<<org.apache.maven>>>, <<<org.apache.maven.plugins>>>,
>> <<<org.apache.maven.reporting>>>
>> +
> 
> Ooops... I've just changed that yesterday on the cargo project. I had the
> groupIds which were following the nested directory structure but I've
> decided to go back to using a single groupid (org.codehaus.cargo) instead
> (http://jira.codehaus.org/browse/CARGO-220).
> 
> My reasons were the following:
> 
> * It's easier for cargo users to have to remember a single groupId
> 
> * In any case as we're using fully qualified artifact id there's no
> possibility of clashing and it's kind of duplicating the information to put
> the hierarchy information both groupId and artifactId.
> 
> * The groupId really represents the project.
> 
> * If we were to use different groupIds using the dotted notation, the m1
> repository on ibiblio would look pretty crowded as we'll have the following
> directories at the top level:
> org.codehaus.cargo/
> org.codehaus.cargo.core/
> org.codehaus.cargo.core.api/
> org.codehaus.cargo.core.containers/
> [...]
> 
> As this is about best practices I'm curious to know what others think. I
> have asked this question on IRC too at that time and Trygve seemed to agree
> with this reasoning.
> 
> Thanks
> -Vincent
> 
> 
> 	
> 
> 	
> 		
> ___________________________________________________________________________ 
> Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
> Téléchargez cette version sur http://fr.messenger.yahoo.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