There are default group Ids that are searched for plugins that are named with the correct artifact Ids.
if the groupId is org.apache.maven.plugin and the artifactId is maven-xyz-plugin and then xyz:goal will work otherwise if the groupId is in the list of plugin group ids specified in your settings.xml (and if you have not specified any then that list is org.codehaus.mojo) for artifacts xyz-maven-plugin the tomcat plugin is org.codehaus.mojo:tomcat-maven-plugin and so it can be found automatically 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 On Wed, Jun 18, 2008 at 9:34 AM, teo.danciu <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm really confused about the declaration of maven plugins in pom.xml. > What is the rule? Why must jetty for instance be declared (otherwise, the > call "mvn jetty:run" results into a build failure) and tomcat can be run > without appearing in pom.xml, while both of them are not core plugins? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Maven-plugins---why-some-of-them-must-be-declared-in-pom.xml-and-some-others-not--tp17967230p17967230.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
