[
https://issues.apache.org/jira/browse/IVY-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608075#action_12608075
]
Tim Berry commented on IVY-733:
-------------------------------
I can still reproduce the original problem with our current build environment
using the 2.0.0-beta2 release, but I no longer see the problem using ivy built
from the latest sources in trunk.
> File system resolver fails to rename artifact directory during atomic publish
> -----------------------------------------------------------------------------
>
> Key: IVY-733
> URL: https://issues.apache.org/jira/browse/IVY-733
> 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
> Assignee: Xavier Hanin
> 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
> 1.0.0.0 -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.
