[jira] Commented: (IVY-970) wrong result when resolve fails

["Michael Kebe (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649615#action_12649615 ] 

Michael Kebe commented on IVY-970:
----------------------------------

WIth the trunk now it is even worse.

The second publish fails now. It tries to publish with version "1.0-dev-b1" although I expect "1.0-dev-b2". So I cannot run the testcase from above.

{code}
publish:
:: delivering :: org.apache.ivy.example#version;working@kebap :: 1.0-dev-b1 :: release :: Fri Nov 21 07:40:11 CET 2008
        delivering ivy file to D:\Temp\multi-project\projects\version\build\ivy.xml
:: publishing :: org.apache.ivy.example#version

BUILD FAILED
D:\Temp\multi-project\common\common.xml:160: impossible to publish artifacts for org.apache.ivy.example#version;working@
kebap: java.io.IOException: file copy not done from D:\Temp\multi-project\projects\version\build\version.jar to D:\Temp\
multi-project\projects\version\..\..\common\..\repository\shared\org.apache.ivy.example\version\1.0-dev-b1\jars\version.
jar: destination already exists and overwrite is false
{code}

What I tried now:
1. publish the version project with "ant publish"
2. change the ivy.xml from the shared repository, so that the hashes are incorrect
3. publish a second time

Here the second publish also fails with the same message from above.

What I expect:
An error message like "The hash (md5, sha1) of the artifact (ivy.xml in this case) is no longer correct and could be manipulated by an evil guy". And the build should fail.

> <ivy:buildnumber> wrong result when resolve fails
> -------------------------------------------------
>
>                 Key: IVY-970
>                 URL: https://issues.apache.org/jira/browse/IVY-970
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0-RC2
>            Reporter: Michael Kebe
>            Assignee: Maarten Coene
>             Fix For: trunk
>
>
> After publishing an artifact to the repository. Ivy uploads an ivy.xml and generates related .md5 .sha1 files.
> With a cleaned ivy cache the buildnumber task gives the wrong result when the ivy.xml in the repository is changed without changing the hash files.
> This is ok, as there is at least a warning. But currently there is nothing. The ivy:buildnumber task runs without a message and returns the "possibly" wrong next revision.

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