From 30074431a762098482cd769359101444fe9e1efa Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Wed, 8 Feb 2017 09:37:29 +0000 Subject: [PATCH] Improve documentation of static resource reloading with devtools Closes gh-5133 Closes gh-7886 --- spring-boot-docs/src/main/asciidoc/howto.adoc | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/howto.adoc b/spring-boot-docs/src/main/asciidoc/howto.adoc index 7e715d125e..edb42b12f8 100644 --- a/spring-boot-docs/src/main/asciidoc/howto.adoc +++ b/spring-boot-docs/src/main/asciidoc/howto.adoc @@ -2452,6 +2452,13 @@ There are several options for hot reloading. The recommended approach is to use <> as it provides additional development-time features such as support for fast application restarts and LiveReload as well as sensible development-time configuration (e.g. template caching). +Devtools works by monitoring the classpath for changes. This means that static resource +changes must be "built" for the change to take affect. By default, this happens +automatically in Eclipse when you save your changes. In IntelliJ IDEA, Make Project will +trigger the necessary build. Due to the +<>, changes to static resources will not trigger a restart of your application. +They will, however, trigger a live reload. Alternatively, running in an IDE (especially with debugging on) is a good way to do development (all modern IDEs allow reloading of static resources and usually also @@ -2459,8 +2466,8 @@ hot-swapping of Java class changes). Finally, the <> can be configured (see the `addResources` property) to support running from the command line -with reloading of static files. You can use that with an external css/js compiler process -if you are writing that code with higher level tools. +with reloading of static files directly from source. You can use that with an external +css/js compiler process if you are writing that code with higher level tools.