@@ -1963,17 +1963,19 @@ requests). To switch that on in a Spring Boot application you just need to set
1963
1963
1964
1964
[[howto-reload-static-content]]
1965
1965
=== Reload static content
1966
- There are several options for hot reloading. Running in an IDE (especially with debugging
1967
- on) is a good way to do development (all modern IDEs allow reloading of static resources
1968
- and usually also hot-swapping of Java class changes).
1966
+ There are several options for hot reloading. The recommended approach is to use
1967
+ <<using-spring-boot.adoc#using-boot-devtools,`spring-boot-devtools`>> as it provides
1968
+ additional development-time features such as support for fast application restarts
1969
+ and LiveReload as well as sensible development-time configuration (e.g. template caching).
1969
1970
1970
- The <<using-spring-boot.adoc#using-boot-devtools,`spring-boot-devtools`>> module is also
1971
- available with support for fast application restarts and LiveReload.
1971
+ Alternatively, running in an IDE (especially with debugging on) is a good way to do
1972
+ development (all modern IDEs allow reloading of static resources and usually also
1973
+ hot-swapping of Java class changes).
1972
1974
1973
1975
Finally, the <<build-tool-plugins.adoc#build-tool-plugins, Maven and Gradle plugins>> can
1974
- be configured to support running from the command line with reloading of static files. You
1975
- can use that with an external css/js compiler process if you are writing that code with
1976
- higher level tools.
1976
+ be configured (see the `addResources` property) to support running from the command line
1977
+ with reloading of static files. You can use that with an external css/js compiler process
1978
+ if you are writing that code with higher level tools.
1977
1979
1978
1980
1979
1981
0 commit comments