Closed GoogleCodeExporter closed 9 years ago
I am also getting this issue with Windows.
Original comment by ecb0...@gmail.com
on 10 Jul 2013 at 5:19
Just want to add...with the GAE instance running in the background after
devserver_start, I tried devserver_stop and the GAE instance still lives on
despite the success message that I received. I then did exactly what the Maven
goal does (send empty POST to /_ah/admin/quit) manually through the browser and
that successfully shuts off the Java process for the background GAE instance.
Hopefully this gets fixed soon. Any acknowledgement of this bug from Google?
Original comment by ecb0...@gmail.com
on 10 Jul 2013 at 5:38
Same with me. I'm able to quit through the URL as well via Fiddler
Original comment by k...@baley.org
on 10 Jul 2013 at 5:40
I cannot really see how, but could stopDevAppServer() be platform dependent?
See
https://code.google.com/p/appengine-maven-plugin/source/browse/src/main/java/com
/google/appengine/devappserver/AbstractDevAppServerMojo.java#200
Original comment by ingo.jae...@gmail.com
on 10 Jul 2013 at 5:43
I think this patch fixes it:
Original comment by tadas.subonis@gmail.com
on 13 Jul 2013 at 11:17
Attachments:
Is there anyway that this change can be applied as some sort of pull request?
Or is that just Github terminology?
Original comment by ecb0...@gmail.com
on 15 Jul 2013 at 7:13
I can confirm this behavior is still present in 1.8.9
Original comment by dajudge...@gmail.com
on 6 Feb 2014 at 7:30
Same issue with 1.9.4. Please resolve this.
Original comment by khid...@gmail.com
on 18 May 2014 at 10:52
Fix will be in 1.9.7
For now, you can
$ git clone https://code.google.com/p/appengine-maven-plugin/
$ cd appengine-maven-plugin
$ mvn install
and use the version 1.9.7-SNAPSHOT in the plugin version as a workaround until
1.9.7 is pushed
Original comment by l...@google.com
on 14 Jun 2014 at 5:32
Still seeing this issue with appengine-maven-plugin:1.9.7 - the devserver won't
stop under Windows 7. Did the changes make it in?
Original comment by jfbib...@gmail.com
on 18 Aug 2014 at 2:17
Original issue reported on code.google.com by
k...@baley.org
on 4 Jul 2013 at 1:31