RE: unclear explanation in Guide to Developing Java Plugins

Take a look at http://maven.apache.org/guides/introduction/introduction-to-plugin-prefi x-mapping.html -Original Message- From: Rice Yeh [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 10, 2006 04:29 To: Maven Users List Subject: Re: unclear explanation in Guide to Developing Java

Re: unclear explanation in Guide to Developing Java Plugins

Hi Rice, Based on my observation, by default, maven will omit the word "maven" and "plugin" from the artifactId to get the prefix. Well Im still not sure about it. Regards, -allan Rice Yeh wrote: Hi Allan, My question is how the prefix "hello" gotten in the example? Regards, Rice On 1/1

Re: unclear explanation in Guide to Developing Java Plugins

Hi Allan, My question is how the prefix "hello" gotten in the example? Regards, Rice On 1/10/06, Allan Ramirez <[EMAIL PROTECTED]> wrote: > > Hi Rice, > > When executing -DupdateReleaseInfo=true, you are actually forcing to use > the latest version of the plugin. And by adding the groupId in th

Re: unclear explanation in Guide to Developing Java Plugins

Hi Rice, When executing -DupdateReleaseInfo=true, you are actually forcing to use the latest version of the plugin. And by adding the groupId in the you are saving it so maven can identify where your plugin belongs. Now, Since maven already knows your plugin, Instead of executing it in a l

unclear explanation in Guide to Developing Java Plugins

Hi, When studing the article Guide to Developing Java Pluginsin http://maven.apache.org/guides/plugin/guide-java-plugin-development.html, there is unclear part on the explanation: the command used to execute a goal is "mv