>the jetty plugin (for v6) is something.mortbay.something:maven-jetty-plugin
>so you need to specify it... for v7 they renamed to jetty-maven-plugin so as
>long as the something.mortbay.something is in your plugin search list you
>can just use jetty: without declaring in your pom
Unless they changed the group, it's not going to matter. The maven-xxx-plugin
vs xxx-maven-plugin is just a convenience to help people, it's not coded
anywhere. If you look at the maven-metadata.xml file in the
org.apache.maven.plugins or org.codehaus.mojo, you can see how the expansion
occurs:
<plugin>
<name>Maven Clean Plugin</name>
<prefix>clean</prefix>
<artifactId>maven-clean-plugin</artifactId>
</plugin>
−
<plugin>
<name>Maven Compiler Plugin</name>
<prefix>compiler</prefix>
<artifactId>maven-compiler-plugin</artifactId>
</plugin>
−
<plugin>
<name>Maven Surefire Plugin</name>
<prefix>surefire</prefix>
<artifactId>maven-surefire-plugin</artifactId>
</plugin>
−
<plugin>
<name>Maven Eclipse Plugin</name>
<prefix>eclipse</prefix>
<artifactId>maven-eclipse-plugin</artifactId>
</plugin>
It simply looks for these files by default, scans the prefix for the entered
plugin and then resolves the artifactId and group from here.
You can short cut lookups of non-default groups by doing something like: mvn
groupId:artifactId:version:goal
