[
http://jira.codehaus.org/browse/MEV-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MEV-578.
------------------------------
Assignee: Carlos Sanchez
Resolution: Duplicate
> Hashes do not match the maven-2.0.6.pom (neither SHA-1, nor MD5).
> -----------------------------------------------------------------
>
> Key: MEV-578
> URL: http://jira.codehaus.org/browse/MEV-578
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Baptiste MATHUS
> Assignee: Carlos Sanchez
>
> Here you have the directory containing the files having problem:
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/
> After having had some problem with some corrupted jars, I just changed our
> archiva repository config policy from "fix" to "fail" to be able to identify
> those corrupted ones.
> That's how I noticed there's a problem with this pom. My build is now failing
> because I can't download this pom.
> Then I wrote some code to check that the problem was here, and not something
> bizarre in my continuum/archiva. And that's confirmed: I tested my code with
> some other hashs & corresponding files of the repo and it's OK for those.
> Here's the hash I found for this pom:
> MD5:3cae531192d8b9e238a48f54d85a921
> SHA1: 1991beed3e182e13521406d5acabf8c8d426
> FTR, at the moment, the incorrect hashs are the following:
> MD5: d8362d761d106222538536dd83694b56
> SHA1: 218016709d90d14b64bfb1de3a86a2247e8873db
> Cheers.
> Let me know if you need more informations.
--
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
