Re: Maven Central Repository & Bad Checksums
On Dec 2, 2010, at 10:02 AM, Anders Hammar wrote: > You should file tickets for Maven Central at [1] instead. > > [1] https://issues.sonatype.org/browse/MVNCENTRAL > Sigh. This is what I get for not reading *closely* (and assuming that things were as they were 11 months ago). So Sonatype is in charge of housekeeping for Maven Central now? I'll close my issues on the Codehaus JIRA and re-open them on Sonatype's JIRA, then. Cheers, --sgp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Central Repository & Bad Checksums
Once upon a time, I filed a JIRA at Codehaus: http://jira.codehaus.org/browse/MEV-641. Eleven months elapsed before someone finally fixed the checksum metadata to match the jar in the repository. Yesterday, I filed another pair of issues: MEV-675 and MEV-676. I was wondering if I have to wait another 11 months before they are addressed.[1] Who is handling these? Is there a labor shortage on handling these issues? Furthermore, it would seem that automating this process would be the answer, as it probably wouldn't be difficult to crawl the repository and check checksums and either (a) add them where they are missing or (b) fix them where they are there and are incorrect. If there's a need, I'll volunteer to do just that. --sgp [1] Just kidding, naturally.
