publish fails when setting  ivy.checksums via a property file
-------------------------------------------------------------

                 Key: IVY-977
                 URL: https://issues.apache.org/jira/browse/IVY-977
             Project: Ivy
          Issue Type: Bug
    Affects Versions: 2.0.0-beta-2
         Environment: Windows XP
            Reporter: Marc De Boeck
            Priority: Minor


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;[EMAIL PROTECTED]: 
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 directory 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.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to