My next question would then be: if we specify the exact version to use in the pom and deploy a plugin using deploy-file then even though the maven-metadata.xml file hasn't been updated/created, can I rely on the build run successfully, using the correct plugin?
TomHuybrechts wrote: > > On Jan 29, 2008 5:32 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > >> On Jan 26, 2008 4:20 PM, nadias <[EMAIL PROTECTED]> wrote: >> > >> > Will this work deploy-file or just deploy? I am working with >> deploy-file but >> > it is not updating the metadata even if I specify this parameter. >> >> The updateReleaseInfo parameter is not listed for the deploy-file goal. >> * >> http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html >> >> Vote for it! http://jira.codehaus.org/browse/MDEPLOY-52 :) >> >> This seems to make it impossible to deploy a working plugin with >> deploy:deploy-file. The 'latest' and 'release' elements seem to be >> required, or Maven complains that it can't find the plugin at all. :( >> > > If you specify an explicit version in your POM, I would think that Maven > always finds it ? > > Tom > > >> >> -- >> Wendy >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/update-creation-of-maven-metadata.xml-file-tp15100044s177p15172352.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]
