[ http://jira.codehaus.org/browse/MEV-422?page=all ] Matt Whitlock reopened MEV-422: -------------------------------
This bug has been marked as fixed with no explanation given, and the problem persists. I direct your attention to a single example: http://www.ibiblio.org/maven2/hsqldb/hsqldb/maven-metadata.xml.sha1 Contents of that file: da39a3ee5e6b4b0d3255bfef95601890afd80709 Actual SHA1 hash of hsqldb/hsqldb/maven-metadata.xml: 47518e66b062e939fa2de433b59797201baf9686 Clearly the problem persists. > Fix the sha1 and md5 checksums for all maven-metadata.xml in repository > ----------------------------------------------------------------------- > > Key: MEV-422 > URL: http://jira.codehaus.org/browse/MEV-422 > Project: Maven Evangelism > Type: Task > Reporter: Matt Whitlock > Assignee: Carlos Sanchez > > > Every maven-metadata.xml.md5 and maven-metadata.xml.sha1 I've looked at in > the repository is invalid. All of the maven-metadata.xml.md5 contain > "d41d8cd98f00b204e9800998ecf8427e", which is the MD5 hash of the empty > string. All of the maven-metadata.xml.sha1 contain > "da39a3ee5e6b4b0d3255bfef95601890afd80709", which is the SHA1 hash of the > empty string. Some script somewhere is not generating these files correctly. > Please fix the script that is responsible for generating these checksum files > for the maven-metadata.xml files, and recursively regenerate the checksums > for the maven-metadata.xml files in the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
