2011/12/17 Antonio Petrelli <antonio.petre...@gmail.com>: > If you release to a staging directory, the Maven metadata (containg info > about previous releases) are not there, so they are created from scratch. > So, after releasing in the staging directory and voting, the copy method > simply overwrite the old metadata with the new one (remember, *without the > old versions*). > So in the end, we needed to use the Maven stage plugin (deprecated), that: > * downloads the staged artifacts; > * reuploads them to the final destination. >
Mark, the above issue mentioned by Antonio is what I think we already encountered with broken maven-metadata.xml. That is https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 More detailed description is in https://issues.sonatype.org/browse/MVNCENTRAL-139 Mark, when you do 7.0 releases, do you scp the maven-metadata.xml file? Do you have all previous releases of 7.0 in your local repository (so that the file is built correctly)? If Nexus allows to prepare new releases without the need to keep old releases around, I am +1 for it. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
