Hi Evan, It sounds like you've picked up the apt-maven-plugin over at Codehaus:
http://mojo.codehaus.org/apt-maven-plugin/ This has an id of org.codehaus.mojo:apt-maven-plugin, whereas the Tobago plugin is org.apache.myfaces.tobago:maven-apt-plugin. You shouldn't have a problem if you've declared the plugin explicitly in your project's pom. The default resolution policy, I believe, is to first look under the org.apache.maven.plugins group id, then any plugin group ids specified in settings.xml's pluginGroups element: http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_settings By the way, the Codehaus apt plugin now supersedes Tobago's plugin: https://issues.apache.org/jira/browse/TOBAGO-656 Cheers, Mark 2008/6/18 Evan Worley <[EMAIL PROTECTED]>: > Hey All, > > I have a general question about the plugin resolution policy. > > For a while now, we've been using the maven-apt-plugin ( > http://myfaces.apache.org/tobago/tobago-tool/maven-apt-plugin/index.html). > To invoke the plugin directly, we would just run "mvn apt:execute". > > Something happened recently, "apt" is being resolved a different plugin > (possibly one that is in the default plugin group id > "org.apache.maven.plugins"). Now "mvn apt:execute" fails, saying that the > goal "execute" is not found in the apt plugin. > > I'm wondering what the policy is for plugin resolution? In my mind, a > dependency should be resolved before a plugin from > "org.apache.maven.plugins" > > What do you all think? > > -Evan > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
