Mvn spring-boot: run vs Run

I am testing spring-boot-devtools using the pusheload function on intelliJ. I have a simple SpringBootApplication that works great.

When I launch the application from the maven command "mvn spring-boot: run", everything works fine, except that the boot server does not start. A message does not appear on the console, and on the chrome extensions the error message "Unable to connect to the download server" is displayed.

If I launch the application using the right mousse button / Run Application.java, everything works fine even with the server. A message appears on the console and the browser can connect to the download server.

Launching the application with the right button of the mousse / Launching the .java application

Console Message

2016-07-13 16:39:47.947  INFO 10440 --- [  restartedMain] o.s.w.s.handler.SimpleUrlHandlerMapping  : Mapped URL path [/**/favicon.ico] onto handler of type [class org.springframework.web.servlet.resource.ResourceHttpRequestHandler]
2016-07-13 16:39:48.026  INFO 10440 --- [  restartedMain] o.s.b.d.a.OptionalLiveReloadServer       : LiveReload server is running on port 35729
2016-07-13 16:39:48.077  INFO 10440 --- [  restartedMain] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2016-07-13 16:39:48.145  INFO 10440 --- [  restartedMain] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started on port(s): 8090 (http)

Launching the application from the mvn command "mvn spring-boot: run"

Chorme extension post:

Could not connect to LiveReload server. Please make sure that a compatible LiveReload server is running. (We recommend guard-livereload, until LiveReload2 comes to your platform.)

Console message. See that the message is not displayed. The LiveReload server runs on the port ....

2016-07-13 16:38:56.749  INFO 6924 --- [           main] o.s.w.s.handler.SimpleUrlHandlerMapping  : Mapped URL path [/**/favicon.ico] onto handler of type [class org.springframework.web.servlet.resource.ResourceHttpRequestHandler]
2016-07-13 16:38:56.852  INFO 6924 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2016-07-13 16:38:56.898  INFO 6924 --- [           main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat started on port(s): 8090 (http)

Why doesn't the maven command start the download server?

+4
source share
1 answer

You need to tell Maven to deploy a separate JVM to run your application, instead of running in the same JVM as Maven:

$ mvn spring-boot:run -Dfork=true
+6
source

All Articles