Hi Benjamin Thank you for test against foo:bar:1.0. Could you take another look at:
http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=748 Revision 748 is a result of deploying version 1.1-SNAPSHOT by Maven 3 http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=759 Next revision 759 is a result of deploying 1.2-SNAPSHOT by Maven 3 http://code.google.com/p/m4enterprise/source/browse/snapshot-repository/com/googlecode/m4enterprise/test1/maven-metadata.xml?r=770 The last revision 770 is a result of deploying 1.3-SNAPSHOT by Maven 2 Only in the last case, when Maven 2 was used for deployment, element "metadata.versioning.release" is defined. For revisions 748 and 759 it doesn't exist. You can checkout the example code from http://m4enterprise.googlecode.com/svn/trunk/test1. Could you tell me where I can find the official reference for maven-metadata format? Has it been changed since Maven 2.x? Thanks, Marcin On 22 December 2010 16:59, Benjamin Bentmann <benjamin.bentm...@udo.edu> wrote: > Marcin Kuthan wrote: > >> You can easily reproduce the issue with direct "mvn deploy:deploy >> -DupdateReleaseInfo=true" call. > > I just ran "mvn deploy:deploy" on a project foo:bar:1.0:pom and got the > expected metadata. So I can only suggest you fill an issue with a complete > example project that eliminates any guess work about your setup. > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
