Spring Boot Maven plugin - spring-boot:run and production

Question

Is it a good idea or practice to start a Spring Boot application at production with a following command of Spring Boot Maven plugin ?

mvn spring-boot:run

For production that would be a bad idea. That would mean you are directly running your code from your repo on production. Instead of a well tested artifact like a jar or war. — M. Deinum, Aug 01 '17 at 06:06
The same question asked in the form of documentation enhancement on GitHub: https://github.com/spring-projects/spring-boot/issues/14395 — fabriziocucci, Sep 10 '18 at 17:22

score 4 · Answer 1 · answered Mar 22 '18 at 14:13

No, this is a bad idea. You would re-build your project on every run which means that you would pull all needed dependencies on each new VM / container.

Also using the spring-boot-maven-plugin in conjunction with the dev-tools for example would lead to options that you don't want in production. This ranges from using other database settings to disabled caching mechanisms for your templating engine.

Use the executable jar instead.

score 0 · Accepted Answer · answered Jul 31 '17 at 21:38

If you want to run the application with the Maven JVM this is fine.

It is just an alternative way to run your application instead of using the executable jar.

As an alternative you could also start your application with gradle

gradle bootRun

Which is best depends on your circumstance. For live production code I would use a versioned executable jar always.

Spring Boot Maven plugin - spring-boot:run and production

2 Answers2