> -----Original Message-----
> From: Rémy Sanlaville [mailto:[email protected]] 
> Sent: 09 April 2009 08:27
> To: Maven Users List
> Subject: Re: Maven Overview Plugin version 1.4 has been released
> 
> >
> > as long as the plugin has its own groupId, the artifactId 
> can be any thing.
> 
> 
> IMHO, even if the plugin has its own groupId, I agree with 
> Stephen that it's better to keep the convention :
> maven-_____-plugin for o.a.m.p plugins
> _____-maven-plugin for other plugins
> 

This was news to me to.  Is this documtented anywhere - prehaps it needs to be 
or made more prominent.

The only thing I could find from google (maven plugin naming conventions) was 
the following two pages neither of which stated this convention. 

http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html

<snip>In other words, when the Maven Plugin Plugin is generating the Plugin 
descriptor for your plugin and you have not explicitly set the goalPrefix in 
your project, the plugin:descriptor goal will extract the prefix from your 
plugin's artifactId when it matches the following patterns: 
${prefix}-maven-plugin, OR 
maven-${prefix}-plugin
</snip>

And 

http://maven.apache.org/guides/mini/guide-naming-conventions.html

Which mentions nothing...  It seems like although codehause standardised one 
_-maven-plugin and maven.a.o standardised on maven-__-plug-in other groups 
haven't standardised on either and they are all a mix

e.g.
        maven-jetty-plug-in (org.mortbay.jetty)
        tools-maven-plugin (org.apache.geronimo.genesis.plugins)
        maven-jaxme-plug-in (org.apache.ws.jaxme)

(also try a quick search in nexus for *-maven-plug-in and maven-*-plug-in - and 
it looks like the hourse has bolted..)


/James

**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the 
addressee only. Any dissemination, copying or distribution of this message or 
any attachments by anyone other than the intended recipient is strictly 
prohibited. If you have received this message in error, please immediately 
notify the [email protected] and destroy the original message. Messages sent 
to and from NDS may be monitored. NDS cannot guarantee any message delivery 
method is secure or error-free. Information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. We do not 
accept responsibility for any errors or omissions in this message and/or 
attachment that arise as a result of transmission. You should carry out your 
own virus checks before opening any attachment. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales Registered no. 
3080780 VAT no. GB 603 8808 40-00
**************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to