Code Server's Process Still Running After Stopping the maven launcher in eclipse

[mamta]

Hi,

I created a gwt project using - mvn archetype:generate -DarchetypeGroupId=net.ltgt.gwt.archetypes -DarchetypeVersion=LATEST -DarchetypeArtifactId=modular-webapp and imported in eclipse. The project is launched with mvn gwt:codeserver -pl -client -am mvn jetty:run -pl -server -am -Denv=dev

As mention in https://github.com/tbroyer/gwt-maven-plugin/issues/110 I added plexus dependency in gwt-maven-plugin. It works fine on the terminal. But in eclipse, it doesn't able to stop the process. Do I need some other settings?

Thanks and regards.

[mamta]

<?xml version="1.0" encoding="UTF-8"?>

4.0.0 com.mamta gwtplayground 1.0-SNAPSHOT pom UTF-8 com.google.gwt gwt 2.8.2 pom import javax.servlet javax.servlet-api 3.1.0 net.ltgt.gwt.maven gwt-maven-plugin false ${project.build.directory}/gwt/launcherDir maven-compiler-plugin 3.1 1.8 1.8 org.eclipse.jetty jetty-maven-plugin 9.4.8.v20171121 net.ltgt.gwt.maven gwt-maven-plugin 1.0-rc-9 true 1.8 true org.codehaus.plexus plexus-utils 3.0.16 maven-source-plugin 3.0.1 attach-sources package jar-no-fork org.apache.tomcat.maven tomcat7-maven-plugin 2.2 gwtplayground-client gwtplayground-shared gwtplayground-server

[tbroyer]

AFAIK, Eclipse forcibly kills processes, preventing JVM shutdown hooks to run; this means that there's no way to fix this. Workarounds include:

• using gwt:devmode with <arg>-noserver</arg> instead of gwt:codeserver; that way you can terminate the process by simply closing the DevMode window
• going to Eclipse's process view and kill the CodeServer process (rather than killing the Maven run)
• using the GWT Eclipse Plugin rather than Maven

[mamta]

Thanks, it helped.