[GRADLE-2262] Improve error message when .gradle directory is deleted during build Created: 01/May/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-rc-3 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Jens Bendisposto | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
My build fails with an exception. The project can be retrieved from https://github.com/bendisposto/probparsers My workaround is to delete the file taskArtifacts/cache.properties.lock
|
Comments |
Comment by Adam Murdoch [ 06/May/12 ] |
I notice that your build script configures the 'clean' task to deletes the .gradle directory. This is not supported: you should not delete the .gradle directory from within Gradle, as Gradle uses this directory to track various pieces of state during the build. The error is complaining that the .gradle directory has been removed from underneath Gradle (the error message could be a bit clearer, admittedly). |
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. |