2009/10/16 Stephen Connolly <[email protected]> > 2009/10/16 Peter Janes <[email protected]> > >> However, I'm not aware of any released version of Maven or any plugin >> that actually treats dependencies this way; Mercury, tested through >> versions-maven-plugin, doesn't appear to either. (But I'd love to be proven >> wrong!) >> > > versions-maven-plugin does not use mercury to resolve the artifacts, it > only uses the same comparison rule as mercury uses... artifact resolution is > provided by the maven core that you are running v-m-p with. >
I think I understand where you are coming from. maven-deploy-plugin updates the metadata whenever there is a deploy... e.g. <metadata> <groupId>org.codehaus.mojo</groupId> <artifactId>versions-maven-plugin</artifactId> <version>1.0-alpha-1</version> <versioning> <latest>1.0</latest> <release>1.0</release> <versions> <version>1.0-alpha-1</version> <version>1.0-alpha-2</version> <version>1.0-alpha-3</version> <version>1.0</version> </versions> <lastUpdated>20090823192735</lastUpdated> </versioning> </metadata> 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. RELEASE corresponds to the /metadata/versioning/release. LATEST corresponds to the /metadata/versioning/latest and the metadata gets updated by the maven-deploy-plugin... there is also some mad fun with respect to merging the metadata from multiple repos... but understanding that is beyond me at quitting time on a friday ;-) -Stephen
