It sounds like you've got it right. It should simply work. what is the contents of maven-metadata.xml for the artifact and version on the remote server? what about the various copies in the local repository?
I will do a quick test as we don't have integration tests for deployment. - Brett On 9/12/05, Mark Hobson <[EMAIL PROTECTED]> wrote: > > I've just svn up'd to the latest m2 and seem to be having issues with > using deployed snapshots of custom plugins that was working > previously. > > I deploy the custom plugin with "m2 -DupdateReleaseInfo=true deploy". > All seems to deploy okay, complete with the new XML metadata files. > > I then delete any local-repo versions of the plugin and delete > plugin-registry.xml to force auto-discovery of my plugin. My > settings.xml is setup with the correct pluginGroup. > > I then run the plugin goal against another project which fails. It > seems to be looking for pom urls of the form xxx-SNAPSHOT.pom, rather > than those that are there of the form xxx-20050912.112423-1.pom, even > though the metadata XML file indicates the snapshot version is indeed > 20050912.112423, build 1. > > Am I doing anything wrong here? > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
