From 4f95486822d07927daed81e7eeb3258c139419cf Mon Sep 17 00:00:00 2001 From: Phillip Webb Date: Tue, 8 Dec 2020 16:31:46 -0800 Subject: [PATCH] Polish note about Maven/Gradle restarts See gh-24271 --- .../spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 2603be0fd59..4044efc5d47 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 @@ -715,8 +715,8 @@ The way in which you cause the classpath to be updated depends on the IDE that y * 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. -By default, the Gradle and Maven plugins fork the application process. +NOTE: If you are restarting with Maven or Gradle using the build plugin you must leave the `forking` set to `enabled`. +If you disable forking, the isolated application classloader used by devtools will not be created and restarts will not operate properly. TIP: Automatic restart works very well when used with LiveReload. <> for details.