[
http://jira.codehaus.org/browse/MNGSITE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNGSITE-128.
--------------------------------
Resolution: Fixed
Assignee: Brett Porter
> Inconsistent, missing docs for maven plugin naming conventions and auto
> operations based on that
> ------------------------------------------------------------------------------------------------
>
> Key: MNGSITE-128
> URL: http://jira.codehaus.org/browse/MNGSITE-128
> Project: Maven Project Web Site
> Issue Type: Improvement
> Reporter: Marshall Schor
> Assignee: Brett Porter
> Priority: Minor
>
> The page
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html has
> a small entry under "shortening the command line" which says that artifactId
> patterns maven-$name-plugin and $name-maven-plugin are treated specially (by
> convention).
> The email of Sep 27, 2008 to maven users list, from Stephen Connolly says
> AFAIK only plugins with the groupId org.apache.maven.plugins are allowed to
> use the maven-______-plugin pattern. I could not find this documented (other
> than on the users email list.).
> The page
> http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html
> says that the conventional mappings only happen for the "maven-$name-plugin"
> style, and don't mention the other style ($name-maven-plugin).
> I recommend using the text from the 1st ref (which seems to be the clearest)
> as a starting point, to augment and expand the text in the 3rd ref.
> The Complete Reference book is missing this information, as well, I believe.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
