Excellent question. I have no GRADLE_OPTS specified, and I'm just using gradlew to compile the gradle distribution, so it would have to depend upon what the snapshot currently being used by the latest wrapper defaults to. I get no warning about the daemon being experimental, so my guess is that I am not using the daemon.
-Spencer ________________________________ From: Adam Murdoch <[email protected]> To: [email protected] Sent: Thursday, September 15, 2011 3:29 PM Subject: Re: [gradle-dev] Tmp directory cleanup under windows failure Are you using the daemon? On 15/09/2011, at 11:57 PM, Spencer Allain wrote: This hasn't happened to me in a long time, but it happened today when building the gradle source, so I figured I'd report it. > >:docs:groovydoc > >FAILURE: Build failed with an exception. > >* What went wrong: >Execution failed for task ':docs:groovydoc'. >Cause: java.io.IOException: Unable to delete directory >C:\gradle\subprojects\docs\build\tmp\groovydoc\org\gradle\plugins\signing\type. >Cause: Unable to delete directory >C:\gradle\subprojects\docs\build\tmp\groovydoc\org\gradle\plugins\signing\type. > >* Try: >Run with --stacktrace option to get the stack trace. Run with --info or --debug >option to get more log output. > >BUILD FAILED > >-Spencer -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
