[
http://jira.codehaus.org/browse/MEV-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MEV-500.
------------------------------
Assignee: Carlos Sanchez
Resolution: Cannot Reproduce
Everything looks fine for me
$ md5sum.exe XmlSchema-1.2.jar
4544bacefdaecffc78c6b59aba6f431e *XmlSchema-1.2.jar
$ cat XmlSchema-1.2.jar.md5
4544bacefdaecffc78c6b59aba6f431e
$ sha1sum.exe XmlSchema-1.2.jar
9a3cc2b18276eb4d0cd86b34afe46d3ef23f10e5 *XmlSchema-1.2.jar
$ cat XmlSchema-1.2.jar.sha1
9a3cc2b18276eb4d0cd86b34afe46d3ef23f10e5
$ gpg --verify XmlSchema-1.2.jar.asc
gpg: Signature made 11/14/06 14:09:35 using DSA key ID DE240A64
gpg: Good signature from "Jochen Wiedmann <[EMAIL PROTECTED]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 69AF C3E5 65D7 C4FF C6B0 C733 6123 33A3 DE24 0A64
> XMLSchema 1.2 has invalid md5 and sha1 files in Maven2 repository
> -----------------------------------------------------------------
>
> Key: MEV-500
> URL: http://jira.codehaus.org/browse/MEV-500
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Thomas Hallgren
> Assigned To: Carlos Sanchez
>
> The XmlSchema-1.2.jar as published in
> http://repo1.maven.org/maven2/org/apache/ws/commons/schema/XmlSchema/1.2/ has
> invalid md5 and sha1 files . Looking at dates it seems it's been replaced
> some 9 days after the md5 and sha1 was uploaded.
> The same file comes with correct md5 and sha1 in the maven 1 repo.
--
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