On 16/01/2012 10:53, Konstantin Kolinko wrote: > 2012/1/16 Mark Thomas <ma...@apache.org>: >> On 16/01/2012 09:43, Mark Thomas wrote: >>> It appears there is a problem with the Nexus release process. Prior to >>> the switch to Nexus, the Maven metedata contained all previous releases >>> [1]. Post the switch to Nexus, none of the previous releases appear in >>> the metadata [2]. >>> >>> The switch to Nexus has, therefore, introduced the very bug to the >>> Tomcat 7.0.x series that the switch to Nexus was meant to avoid [3]. >>> >>> Given that we go have the prior metadata, how do we get Nexus to use it? >>> >>> [1] > http://repo2.maven.org/maven2/org/apache/tomcat/tomcat-catalina/maven-metadata.xml >>> [2] > https://repository.apache.org/service/local/repositories/orgapachetomcat-078/content/org/apache/tomcat/tomcat-catalina/maven-metadata.xml >>> [3] https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 > > There is no error in that. The metadata is only for > "orgapachetomcat-078" repository that contains this only release and > nothing else.
Hmm. I guess that makes sense but I'm not entirely comfortable with that. I'd rather see the full meta-data before the release like we used to with the scp-copy process. >> Oh, and if there is a way to get Nexus not to create .md5 and .sha1 >> files for the .asc signatures that would be nice but not essential since >> the scp+rsync had the same problem. >> > > I think that it is not possible to avoid creating them. > I've read on dev@commons that it is possible to delete them (more below). Manual deletion is a PITA. We published them before and I am happy to continue to do so. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
