ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Berry (JIRA)" <>
Subject [jira] Created: (IVY-733) File system resolver fails to rename artifact directory during atomic commit
Date Tue, 12 Feb 2008 10:14:07 GMT
File system resolver fails to rename artifact directory during atomic commit

                 Key: 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

I am attempting to use the new atomic commit 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'.

I am using the following ivy settings:

	<settings defaultResolver="Mustang" latest="latest-revision" circularDependencyStrategy="error"
defaultConflictManager="strict" defaultBranch="trunk" />
	<cache lockStrategy="artifact-lock" />
		<chain name="Mustang">
			<filesystem name="Permanent" transactional="true">
				<ivy pattern="${repository.dir}\Permanent\[module]\[branch]\[revision]\ivy.xml" />
				<artifact pattern="${repository.dir}\Permanent\[module]\[branch]\[revision]\[artifact](.[ext])"
			<filesystem name="Nightly" transactional="true">
				<ivy pattern="${repository.dir}\Nightly\[module]\[branch]\[revision]\ivy.xml" />
				<artifact pattern="${repository.dir}\Nightly\[module]\[branch]\[revision]\[artifact](.[ext])"

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