[GRADLE-2499] Cannot copy archives in compareGradleBuilds Created: 26/Sep/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
I added some Jar tasks as artifacts to the archives configuration and run a compareGradleBuilds to see the difference between building with 1.0 and 1.2.
Unfortunately after the targetBuild was run, I got the following error:
Though it says "after copy to", the file 'master\tmp-filestorage-compareGradleBuilds-1348658101088\target_qs_sharedJar\qs_shared_5.0.RC0.jar' is not present.
|Comment by Björn Kautler [ 26/Sep/12 ]
debug logging also doesn't add more information
|Comment by Peter Niederwieser [ 16/Oct/12 ]
Could be a file locking problem, especially since it occurs on Windows. FileUtils deletes the target file if the source file can't be removed. That's why you don't see the target file.
|Comment by Björn Kautler [ 30/Nov/12 ]
Hm, maybe the "improved cleaning strategy for windows" introduced at http://issues.gradle.org/browse/GRADLE-2244 should also be used for this feature.
|Comment by Björn Kautler [ 21/Apr/14 ]
Actually it wouldn't have improved the situation in my particular case.
And probably the "improved cleaning strategy for windows" would still make sense to be implemented here?
|Comment by Benjamin Muschko [ 15/Nov/16 ]
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.