GAE_ENV + GAE_RUNTIME about gradle-appengine-plugin HOT 8 OPEN

Are you sure about this one? I still think this is properly the domain of dev_appserver.

from gradle-appengine-plugin.

Since we launch the process, we have to handle it. This gradle-appengine-plugin (appcfg based) actually just calls into KickStart https://github.com/GoogleCloudPlatform/gradle-appengine-plugin/blob/master/src/main/groovy/com/google/appengine/task/RunTask.groovy#L102 so it should already be handled, but it's though a convoluted process that I'd rather not deal with in appengine-plugins-core.

from gradle-appengine-plugin.

close?

from gradle-appengine-plugin.

@ludoch handled by kickstart in this plugin already.

from gradle-appengine-plugin.

Ok... I guess if you CTRL-C a run session with gradle, do you know if all processes are killed?
Or maybe this is fixed now? http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4770092

from gradle-appengine-plugin.

The way the gradle plugin is written is that it's only a 2 process chain, so it's fine. It's not calling kickstart.sh : https://github.com/GoogleCloudPlatform/gradle-appengine-plugin/blob/master/src/main/groovy/com/google/appengine/task/RunTask.groovy#L102

from gradle-appengine-plugin.

leaving open to make sure this works.

from gradle-appengine-plugin.

this should be checked for 1.9.56

from gradle-appengine-plugin.