2012/2/17 Mark Thomas <ma...@apache.org>: > Jean-Frederic, > > Post [1] the Tomcat 6 Maven metadata is still incomplete. I thought the > point of going through all that upheaval was to resolve [2]. How come > things are still broken and what is the plan to fix [2]? > > If anyone knows how to poke Nexus to include all versions in the > metadata rather than the last two please shout now. > > Mark > > [1] https://issues.apache.org/jira/browse/INFRA-4162 > [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=52124 >
I do not know how to fix it. Just a few pointers: 1. The metadata files at nexus are broken as well. Two examples: (I do not know whether these are correct URLs that Maven Central syncs from, but they look like it) [3] https://repository.apache.org/service/local/repositories/releases/content/org/apache/tomcat/catalina/maven-metadata.xml [4] https://repository.apache.org/service/local/repositories/releases/content/org/apache/tomcat/catalina-ha/maven-metadata.xml Both [3] and [4] list 6.0.33, 6.0.35 only. I think it is the same for all Tomcat 6 modules. For further reference, the list of modules for Tomcat 6 is the following [[[ <groupId>org.apache.tomcat</groupId> <artifactId>annotations-api</artifactId> <artifactId>catalina</artifactId> <artifactId>catalina-ha</artifactId> <artifactId>coyote</artifactId> <artifactId>dbcp</artifactId> <artifactId>el-api</artifactId> <artifactId>jasper</artifactId> <artifactId>jasper-el</artifactId> <artifactId>jsp-api</artifactId> <artifactId>juli</artifactId> <artifactId>servlet-api</artifactId> <artifactId>tribes</artifactId> <groupId>org.apache.tomcat.extras</groupId> <artifactId>juli-adapters</artifactId> <artifactId>juli</artifactId> ]]] 2. I looked through Infra JIRA looking for Nexus issues. The goal was to find whether anyone had similar problem of incorrect files stored on Nexus. The only issue that I noticed is the following one. Unfortunately it is not yet resolved: [5] https://issues.apache.org/jira/browse/INFRA-3901 [6] https://repository.apache.org/content/repositories/releases/org/apache/ant/ant-apache-log4j/ The issue is that files at [6] are broken, e.g. [6]/1.7.0/ant-apache-log4j-1.7.0.pom is not an XML file at all, but an md5 file. The issue [5] does not mention it, but metadata at [6]/maven-metadata.xml is broken in the same manner as Tomcat 6 one. 3. I think we need to create an INFRA issue for it just to track progress. There is repository @a.o mailing list. I think it is a place to ask & poke, but I do not see much activity there. For reference - subscription information and archive: [7] http://www.apache.org/dev/repository-faq.html#resources [8] http://mail-archives.apache.org/mod_mbox/www-repository/ The [5] issue is unresolved since August 2011... 4. The following issue in Nexus FAQ may be related: [9] https://docs.sonatype.com/display/SPRTNXOSS/Nexus+FAQ -> "Q. The "latest" and "release" tags in maven-metadata.xml are not being updated after deploying artifacts" <quote> A. The maven-metadata.xml files are not updated by Nexus during deployment, they are updated by Maven. It downloads the file, updates it, and then redeploys it. (...) </quote> Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
