ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Commented: (IVY-733) File system resolver fails to rename artifact directory during atomic publish
Date Wed, 25 Jun 2008 14:42:46 GMT


Xavier Hanin commented on IVY-733:

I've added more tests, more messages, more checks against failure to try to prevent this and
better diagnose when something goes wrong. I've also added a check to see if the final destination
directory already exist before starting the transaction, which makes the final move impossible.
This is probably what was causing the problem for you. Could you try again the trunk version
and tell if it fails with a clean message?

> File system resolver fails to rename artifact directory during atomic publish
> -----------------------------------------------------------------------------
>                 Key: IVY-733
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-2
>         Environment: Windows XP Professional SP2 and Windows Vista Ultimate.
> Java version 1.6.0_04.
> Ivy running standalone (called from MSBuild scripts.)
>            Reporter: Tim Berry
>             Fix For: 2.0-RC1
>         Attachments: ivysettings.Nightly.xml
> I am attempting to use the new atomic publishing functionality in the filesystem resolver
(fix for IVY-492.)
> The publishing process appears to complete, and does not show any errors, but the artifacts
are left in a directory named '[revision].part'.
> See attached file for the ivy settings I am using.
> I am running Ivy from an MSBuild script using a command line like the following:
> java.exe -cp ivy.jar;commons-cli.jar -Drepository.dir=C:\Temp org.apache.ivy.Main -settings
ivysettings.Nightly.xml -ivy ivy.xml -revision -publish Nightly -deliverto build\ivy.xml
-status integration -publishpattern build\[artifact](.[ext])

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

View raw message