How to realize Hot deployment by integrating devtools in SpringBoot

In this issue, the editor will bring you about how to achieve hot deployment through the integration of devtools in SpringBoot. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

1. Maven dependency

Org.springframework.boot spring-boot-devtools true

2. When devtools is configured, any file items we modify in classpath will be restarted automatically.

(1) some resources do not necessarily need to trigger a restart when they are changed. For example, Thymeleaf templates can be edited in place. By default, changing the resource path includes: / META-INF/maven, / META-INF/resources, / resources, / static, / public, or / templates does not trigger a reboot, but triggers a real-time reload.

If you reverse exclude these paths, you can use the following configuration:

Spring.devtools.restart.exclude=static/**,public/**

(2) if you want to keep these default values and add other exclusions, use the spring.devtools.restart.additional-exclude property instead.

(3) through the System.setProperty ("spring.devtools.restart.enabled", "false"); method, you can turn off devtools when the SpringApplication.run () method is running.

(4) when we start App.java again, the loader used becomes restartedMain, indicating that the hot deployment has been successful.

Ps: other ways:

True

Examples are as follows

Org.springframework.boot spring-boot-maven-plugin true above is how to achieve hot deployment by integrating devtools in SpringBoot shared by Xiaobian, if you happen to have similar doubts. It may be understood with reference to the above analysis. If you want to know more about it, you are welcome to follow the industry information channel.