Killing gradle with ctrl+c leaves node process running

laurimak commented 9 years ago

Start gulp with

gradle gulp_<whatever>

End process with ctrl+c.

-> node process is left running background

gradle --version

------------------------------------------------------------
Gradle 2.1
------------------------------------------------------------

Build time:   2014-09-08 10:40:39 UTC
Build number: none
Revision:     e6cf70745ac11fa943e19294d19a2c527a669a53

Groovy:       2.3.6
Ant:          Apache Ant(TM) version 1.9.3 compiled on December 23 2013
JVM:          1.8.0_25 (Oracle Corporation 25.25-b02)
OS:           Windows 7 6.1 amd64

buildscript {
  dependencies {
    classpath 'com.moowork.gradle:gradle-node-plugin:0.8'
    classpath 'be.filipblondeel.gradle:gradle-gulp-plugin:0.1'
  }
}

srs commented 9 years ago

Hi, could you make a pull request for your fix in gradle-node-plugin?

nedtwigg commented 8 years ago

+1 on this problem, as of v0.11. Especially bothersome for gulp watch sorts of things. I don't see how the referenced commit fixes the problem. Love the plugin!

alethenorio commented 8 years ago

I don't think this is an issue in the gulp plugin. I am having the same issue with webpack as well where it leaves the dev server running in the background (I am using a linux machine). Really annoying.

srs / gradle-gulp-plugin

Killing gradle with ctrl+c leaves node process running #1