FWIW, that's what I've done for the Cactus plugin (I've named it cactus-maven-plugin). But that's because there is only 1 plugin. If I had more than 1 I would have named it: cactus-tomcat-maven-plugin or cactus-maven-tomcat-plugin.
I use the same approach: <myproject>-maven-plugin. If I had more than one I'd go for <myproject>-<myplugin>-maven-plugin. If I needed to deliver plugins for some other software I'd use: <myporject>-<targetsoftware>-plugin or <myproject>-<myplugin>-<targetsoftware>-plugin
Conflicting plugin names can surely are a problem. GroupId does not help much, because the plugins are identified by artifactId and version when stored and unpacked in $MAVEN_HOME/plugins and $MAVEN_HOME_LOCAL/plugins respectively. Therefore it's wise to use codeczar-tomcat-maven-plugin style names.
Conflicting goal names are also hard to avoid except if you include some sort of namespace in them: codeczar-tomcat:start. A bit verbose, but safe.
R.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
