[IVY-977] error message is not clear when specifying an invalid value for checksums

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0-beta-2
• Fix Version/s: 2.1.0-RC1

Environment

• Windows XP
• java version "1.5.0_14"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
  Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode, sharing)
• Apache Ant version 1.7.0 compiled on December 13 2006

• Assignee: Maarten Coene
• Reporter: Marc De Boeck
• Created: 25/Nov/08 14:48
• Updated: 17/Mar/09 22:31
• Resolved: 26/Nov/08 22:52

Description

When setting the property ivy.checksums in a property file, each publish operation failed with the following error:

publish:package:
[echo] >>> Publishing main package to local repository
[ivy:publish] :: publishing :: com.bene_system#common2-message
[ivy:publish] publish aborted: deleted R:\ext950_r_costa_INCEPTION_int_dn\devtools\oobs\var\my_local_repo\com.bene_system\common2-message\20081125153702.part

BUILD FAILED
R:\ext950_r_costa_INCEPTION_int_dn\devtools\oobs\oobs-java.xml:786: The following error occurred while executing this line:
R:\ext950_r_costa_INCEPTION_int_dn\devtools\oobs\oobs-java.xml:787: impossible to publish artifacts for com.bene_system#common2-message;working@PO060001737: java.io.IOException: The filename, directory name, or volume label syntax is incorrect

Total time: 3 seconds

My ivysettings-file looked as follow:
<ivysettings>
<properties file="${ivy.settings.dir}/var/default.properties"/>
....
</ivysettings>

In the property file default.properties ivy.checksums was defined as follows:
ivy.checksums = ""

Even when setting ivy.checksums="md5, sha1" or any other value, the build still failed.

I then tried to set the property directly in the ivysettings file:
<ivysettings>
<properties file="${ivy.settings.dir}/var/default.properties"/>
<property name="ivy.checksums" value="" />

And that worked fine.
So there is a workaround, but it took me a very long time to find out the root cause of this failure. So I propose that at least this is documented somewhere.