[
http://jira.codehaus.org/browse/MEV-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213322#action_213322
]
A commented on MEV-633:
-----------------------
So 2.0.x users should be screwed?
First the biggest non-sense in maven I've seen is to accept an artifact with
wrong checksums by default. And then why use a less efficient checksum format
when that is breaking compatibility badly?
> Wrong sha1 sum of xalan-2.7.1.jar
> ---------------------------------
>
> Key: MEV-633
> URL: http://jira.codehaus.org/browse/MEV-633
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
> Reporter: Stepan Koltsov
> Assignee: Benjamin Bentmann
>
> http://mirrors.ibiblio.org/pub/mirrors/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.sha1
> has contents:
> ===
> SHA1(xalan-2.7.1.jar)= 75f1d83ce27bab5f29fff034fc74aa9f7266f22a
> ===
> should have:
> ===
> 75f1d83ce27bab5f29fff034fc74aa9f7266f22a
> ===
> same problem for
> http://mirrors.ibiblio.org/pub/mirrors/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar.md5
> http://mirrors.ibiblio.org/pub/mirrors/maven2/xalan/serializer/2.7.1/serializer-2.7.1.jar.sha1
> and other files.
--
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
