ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <gscok...@gmail.com>
Subject Re: Overriding a bad checksum
Date Thu, 15 May 2008 18:40:24 GMT
You can also update the checksum attribute of the resolver if you have
your own settings file.
See http://ant.apache.org/ivy/history/latest-milestone/configuration/resolvers.html



2008/5/15 Nicolas Lalevée <nicolas.lalevee@hibnet.org>:
>
> Le 15 mai 08 à 20:14, Marshall Pierce a écrit :
>
>> A handful of packages I'm trying to use have invalid md5 checksums on
>> repo1.maven.org, e.g.:
>>
>> [ivy:resolve]   problem while downloading module descriptor:
>> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.pom:
>> invalid md5: expected=\7986af8834017fafae425331b9d2dc6f
>> computed=7986af8834017fafae425331b9d2dc6f (799ms)
>>
>> When I check the .md5 file
>> (http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.jar.md5),
>> sure enough, there is a spurious \ at the beginning. Clearly, the file is
>> actually valid, since the computed md5 would be the same as the expected md5
>> if it didn't have the \ in front. How can I get the resolver to ignore the
>> "bad" md5?
>>
>
> You can set the variable ivy.checksums to "".
>
> http://ant.apache.org/ivy/history/latest-milestone/configuration/resolvers.html#common
> http://ant.apache.org/ivy/history/latest-milestone/concept.html#checksum
>
> Nicolas
>
>



-- 
Gilles Scokart

Mime
View raw message