2009/10/16 Benjamin Bentmann <[email protected]> > Stephen Connolly wrote: > > maven-deploy-plugin updates the metadata whenever there is a deploy... >> e.g. >> >> it sets the /metadata/versioning/latest to the version that is has just >> deployed. and if the version is not a SNAPSHOT, it sets the >> /metadata/versioning/release as well. >> > > Actually, it's a little more complicated ;-) . The <latest> tag is not > updated by the maven-deploy-plugin itself but controlled by metadata and the > maven-plugin-plugin is the only plugin that sets this version in the > metadata. > > And for the <release> tag, that gets not updated depending on SNAPSHOT or > not but depending on the parameter updateReleaseInfo of the > maven-deploy-plugin. The flag is usually set to true via the release > profile. >
Well I'd like to say that I'd simplified the explanation so that people just "got it" about keep well away from LATEST and RELEASE... but the fact is I did not realize it was more messy than my explanation! ;-) > So yes, I second your suggestion to use version ranges instead of these > magic versions which AFAIK were only meant to support the automatic plugin > version resolution and not dependency resolution in general. > > > Benjamin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
