Because Maven tries to resolve the "short" name by looking at the maven-metadata.xml file stored in org.apache.maven and then org.codehaus.mojo (you may also define a pluginGroup in your settings). The jetty plugin is not in one of those groups, so it's not found...unless it's in your pom or there's an org.mortbay pluginGroup in your settings.
-----Original Message----- From: teo.danciu [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 4:35 AM To: [email protected] Subject: Maven plugins - why some of them must be declared in pom.xml and some others not? 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
