I fixed some code related to the plugin prefixes in http://jira.codehaus.org/browse/MNG-2926. This is currently in 2.0.7-SNAPSHOT, I wonder if it might be fixed at the same time.
--Brian -----Original Message----- From: ertnutler [mailto:[EMAIL PROTECTED] Sent: Friday, June 01, 2007 6:40 AM To: users@maven.apache.org Subject: plugin shorthand not working as expected I've read through and followed this: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefi x-mapping.html I have a custom plugin whose groupId I've configured in a custom pluginGroup in my <m2_home>/conf/settings.xml like so: <pluginGroups> <pluginGroup>com.mycompany.maven.plugin</pluginGroup> </pluginGroups> In the generated plugin.xml, I have <goalPrefix>promotion</goalPrefix> and <goal>promote</goal>. The problem is that unless I install this file to my local repo by building it locally, I can't use the shorthand notation to invoke it. In other words, when I install the plugin to my local repo, this command works fine: mvn promotion:promote But when I delete the artifact from my local repo and run the same command, I get the following output. (Using the fully qualified notation results in the plugin being invoked as normal, so I know that the plugin is in my central repo.) Here's the relevant output: [INFO] Searching repository for plugin with prefix: 'promotion'. [INFO] com.mycompany.maven.plugin: check for updates from central [INFO]------------------------------------------------------------------ --------- [ERROR] BUILD ERROR [INFO]------------------------------------------------------------------ --------- [INFO] The plugin 'org.apache.maven.plugins:maven-promotion-plugin' does not exist....' It appears that the <pluginGroup> is being resolved, but I can't figure out why Maven doesn't resolve the shorthand unless I install locally. Any ideas? -- View this message in context: http://www.nabble.com/plugin-shorthand-not-working-as-expected-tf3851536 s177.html#a10910448 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]
