On 16 January 2012 10:53, Konstantin Kolinko <knst.koli...@gmail.com> 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. > > I do not know an easy way to find similar current repositories in > other projects. Just searched markmail.org for recent VOTE threads > mentioning repository.apache.org. > > Here are two examples > https://repository.apache.org/content/repositories/orgapacherave-015/ > https://repository.apache.org/content/repositories/maven-060/ > > (from the following threads: > http://markmail.org/thread/qt5pwg3xdxpapyc5 > http://markmail.org/thread/jaa3fi4djn6kflic > ) > >> >> 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 thought I had raised a bug against Nexus for that, but cannot find it at present. Likewise, Maven should not create them. [They are only small, but they are a nuisance when visually scanning the directory listing] > I've read on dev@commons that it is possible to delete them (more below). > > I think that Maven may need those files just to autocheck integrity of > asc files downloaded from remote servers. So I think it is better to > keep them. AFAIK that's not necessary. > > Regarding the procedure to delete those files I just did some search: > Some [1] say that you delete them "before closing staging area". > Others [2] (an older thread but seems more reliable) say that only > after closing it. It used to be possible to delete spurious files in both open and closed staging areas. It's no longer possible to delete files in the open state; I've raised a bug for this: https://issues.apache.org/jira/browse/INFRA-4312 > [1] http://markmail.org/message/tebuldnggk3pepky > [2] http://markmail.org/thread/uqjxxvpgztrlg362 > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
