[
https://issues.apache.org/jira/browse/ARIES-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843304#action_12843304
]
Graham Charters commented on ARIES-230:
---------------------------------------
I did wonder, but there are so many examples which follow the
maven-xxx-plugin, that aren't 'official'. Tuscany has 7, for example
:-S . I had a quick hunt for guidance and found the following link:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
. It describes how to create the maven-hello-plugin (using their
convention) and it states the following which suggests both naming
styles are 'official' but doesn't say they should be avoided.
"The "maven-$name-plugin" and "$name-maven-plugin" artifactId patterns
are treated in a special way. If no plugin matches the artifactId
specified on the command line, Maven will try expanding the artifactId
to these patterns in that order. So in the case of our example, you
can use "mvn sample.plugin:hello:sayhi" to run your plugin. Note:
these 2 patterns are used respectively by the official Maven 2 plugins
and the Mojo project plugins."
Can you point me at some guidance to make sure we don't end up with
multiple renames?
Many thanks.
Graham.
> Rename eba-maven-plugin to maven-eba-plugin for consistency
> -----------------------------------------------------------
>
> Key: ARIES-230
> URL: https://issues.apache.org/jira/browse/ARIES-230
> Project: Aries
> Issue Type: Improvement
> Components: Application
> Affects Versions: 0.1
> Reporter: Graham Charters
> Assignee: Graham Charters
> Priority: Trivial
> Fix For: 0.1
>
>
> Rename eba-maven-plugin to maven-eba-plugin for consistency
> Also need to change any samples that use the current plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
