On Tue, Sep 18, 2012 at 10:47 PM, Hans Dockter <[email protected]>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. > Here we go: gradle -v ------------------------------------------------------------ Gradle 1.3-20120918133742+0000 ------------------------------------------------------------ Gradle build time: Tuesday, September 18, 2012 1:37:42 PM UTC Groovy: 1.8.6 Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012 Ivy: 2.2.0 JVM: 1.6.0_35 (Apple Inc. 20.10-b01-428) OS: Mac OS X 10.8.1 x86_64 1.) No daemon startet up and calling gradle jettyRun Output: :classes UP-TO-DATE > Building > :jettyRun > Running at http://localhost:8080/quickstart jps: 53026 GradleMain 53033 GradleDaemon After ctrl-c jps yields no daemon processes. Is that the intendent behaviour. 2.) What I can't reproduce right now, but I'm pretty sure happened yesterday a couple of time is that ctrl-c is stopping the build but not shutting down jetty and the daemon was still running. Then running another build created another daemon process. Hans > Hans > > >> Cheers! >> -- >> Szczepan Faber >> Principal engineer@gradleware >> Lead@mockito >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >>
