It seems that using the Jetty plugin with the daemon is not in the best shape: http://issues.gradle.org/browse/GRADLE-2263
As we strongly recommend to use the daemon for development machines I think this is a critical bug. - When you stop Jetty, it kills the daemon - Jetty is often not killed after ctrl-c. - When you trigger another build another daemon is fired up and the build fails because Jetty is already running. I think this should have a high priority for 1.3. Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleware CEO, Gradleware - Gradle Training, Support, Consulting http://www.gradleware.com
