ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Garrison <jim.garri...@troux.com>
Subject Ivy confused about sha1 vs md5 checksums?
Date Thu, 30 Jun 2011 21:16:16 GMT
We just started getting the following error when resolving from a local repository:

[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve]           [FAILED     ] commons-io#commons-io;1.4!commons-io.jar: invalid sha1:
expected=<!doctype computed=a8762d07e76cfde2395257a5da47ba7c1dbd3dce (827ms)
[ivy:resolve]           [FAILED     ] commons-io#commons-io;1.4!commons-io.jar: invalid sha1:
expected=<!doctype computed=a8762d07e76cfde2395257a5da47ba7c1dbd3dce (827ms)
[ivy:resolve]   ==== public: tried
[ivy:resolve]     http://devmaster:8081/nexus/content/groups/public/commons-io/commons-io/1.4/commons-io-1.4.jar

devmaster is a local caching Nexus server.

commons-io.jar has only md5 checksums in Maven Central, not sha1.  I purged the locally cached
copy from devmaster and tried again but got the same error.

After a little digging through the Ivy docs, I added the following line to ivysettings.xml:

      <property name="ivy.checksums" value="md5,sha1"/>

to force Ivy to try md5 first, which fixed the problem.

It looks like Ivy is somehow being fooled into thinking it needs to verify an sha1 sum when
no such checksum exists.  Known problem?

Mime
View raw message