Thanks for your input. I launch Maven using a Maven Build run configuration (which comes with m2e). Would you suggest another approach?
During the invoked Maven process, the appengine-maven-plugin will launch a Jetty server on which the application is deployed. In contrast to most other use cases, I guess, the Maven process itself keeps running and will not terminate on its own. In a Windows shell, I would send a termination signal with Ctrl+C, which causes a clean shutdown of the Jetty server and the Maven process. In Eclipse, however, the terminate button seems to instantly kill the launched process instead of allowing it to properly shut down. As a consequence, the Maven process cannot terminate any child processes before exiting, e.g., the Jetty server launched by the appengine-maven-plugin. Other people have had trouble with this lack of a possibility for proper termination in the context of similar Maven plugins that launch a dedicated server instead of merely deploying on one that is already running:
http://jira.codehaus.org/browse/JETTY-208