Hans Dockter-2 wrote > Am Dienstag, 18. September 2012 schrieb Szczepan Faber : > >> >http://issues.gradle.org/browse/GRADLE-2263 >> >> AFAICT, the issue above is unrelated to the 'Gradle build daemon'. >> >> > - When you stop Jetty, it kills the daemon >> >> You mean the build daemon here? I thought we fixed that a couple of >> releases ago. Jetty stopper used to do System.exit() :) > > > Yes. I mean the build daemon. I have tried with latest from master. > > I will provide a more detailed description tomorrow if it helps. > > Hans > > >> Cheers! >> -- >> Szczepan Faber >> Principal engineer@gradleware >> Lead@mockito >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >>
The linked JIRA ticket is unrelated to the build daemon. The issue arises when 'daemon=true' is set on the jetty task which allows the server to run in the background while the build continues (to execute tests, etc). Perhaps confusion between the jetty daemon and the build daemon was what caused the change that introduced this behavior... In any case, it seems that the jetty watcher should be started. I don't think it uses System.exit() to kill the service so it should be safe (it is when I call it as shown in the workaround). thanks - ray -- View this message in context: http://gradle.1045684.n5.nabble.com/Jetty-and-the-daemon-tp5710214p5710219.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
