Eclipse's "Terminate" `spring-boot:run` doesn't terminate Tomcat

[raphinesse]

Execute spring-boot:run via an Eclipse maven build run configuration. Hit the "Terminate" button on Eclipse's "Console" view.

Expected: Maven and Spring application are stopped
Actual: Maven is stopped, but Tomcat still listens

Spring Boot 1.1.4.REALEASE
Eclipse Luna - Java EE
Windows 7

[dsyer]

The best way to "fix" that is to not do it. Why would you need to run a maven goal from eclipse when you can just right click in the main class and Run As->Java Application?

[raphinesse]

Run As->Java Application has worked for me from the start. I just somehow thought that the maven goal would be safer (installing dependencies, etc.). But if it's ok to just run it as a Java Application in all cases, I'm perfectly fine with that 😁

[dsyer]

Works for me. Thanks for the feedback.

[tornabene]

Same problem into ubuntu 14.04 64BIT Eclipse Luna spring boot 1.1.8.RELEASE

[tornabene]

Into spring-boot 1.0.2 work perfect

[dsyer]

Then why not follow the advice above (don't use the maven plugin to run your app)?

Also see #1412 (you can configure the plugin not to fork now).

[odedpeer]

When you run the Spring Boot plugin you get hot deploy of code. When you run your application as a Java process you lose this capability

[snicoll]

This issue was closed over 6 months ago. If you want to get noticed, please make sure to comment on an opened issue (or create one of your own). I'd argue for the exact opposite actually so if you create an issue, please make sure to provide enough details about your setup.

[zteater]

dev-tools (in particular hot swapping) does not work when running as an application alone. There seems to be 2 work arounds. 1) on console terminate, manually terminate Java process for tomcat 2) execute mvn spring-boot:run in a terminal outside of eclipse.

[jordihs]

For reference of future visitors of this thread: to avoid forking the process and thus fully stopping spring boot from eclipse, open "run configurations", edit the maven launch you defined for your project, and under the "JRE" tab, add -Dfork=false to the VM arguments text area.

[gsugambit]

@jordihs I'm not sure why you aren't getting more praise here. Thanks for pointing this out as i was about ready to either 1) not use dev tools or 2) always run it outside of eclipses. Appreciate it a lot man

[gsugambit]

@jordihs actually it not really working lmfao