From 0503079dc596ce974df17b21944725896f1747b1 Mon Sep 17 00:00:00 2001 From: "Billy T. Hernandez" Date: Sun, 29 Nov 2020 00:16:28 -0800 Subject: [PATCH] Document devtools restart with Maven/Gradle Update the documentation to help avoid confusion for people who aren't using an IDE. See gh-24271 --- .../spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc index 1b1dd12ab3..11a6731b6c 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc @@ -711,6 +711,7 @@ As DevTools monitors classpath resources, the only way to trigger a restart is t The way in which you cause the classpath to be updated depends on the IDE that you are using. In Eclipse, saving a modified file causes the classpath to be updated and triggers a restart. In IntelliJ IDEA, building the project (`Build +->+ Build Project`) has the same effect. +If using a build plugin, running `mvn compile` for Maven or `gradle build` for Gradle will trigger a restart. **** NOTE: As long as forking is enabled, you can also start your application by using the supported build plugins (Maven and Gradle), since DevTools needs an isolated application classloader to operate properly.