On 17/08/10 6:44 PM, Magnus Rundberget wrote:
Hi,
I know this is work in progress, but thought I'd provide some input.
I downloaded gradle-0.9-20100729113141+0200 which I got from a link in
a tweet from GradleOrg.
I'm running gradle on cygwin (windows xp).
When running with the daemon clean build works fine the first time,
but running it a second time doesn't work since it seems the running
jvm process must have file locks on target/builddir directories/files.
(typically "unable to delete xx") Killing the running jvm and running
clean build again works, but sort of defeats the purpose.
There's definitely a few issues with the build daemon at this stage.
It's really only a prototype to verify that the approach does actually
make things faster. I wouldn't really be using it in production at this
stage, though it's probably ok for doing proof-of-concept work on unix
platforms.
We know about a few locking issues on Windows from our integration
tests. No doubt there are more. There are also some heap and permgen
leaks. Of course, we will fix these before we make using the build
daemon the default mode.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
