From 4eb73e0050891828584e9a588742d72586c11025 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Mon, 4 Mar 2019 15:57:47 +0100 Subject: [PATCH] Recommend that DevTools is excluded with custom packaging arrangement Closes gh-15382 --- .../src/main/asciidoc/using-spring-boot.adoc | 11 +++++++---- 1 file changed, 7 insertions(+), 4 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 bf2ae501c7e..e66eddd5087 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 @@ -762,10 +762,13 @@ listings for Maven and Gradle: NOTE: Developer tools are automatically disabled when running a fully packaged application. If your application is launched from `java -jar` or if it is started from a -special classloader, then it is considered a "`production application`". Flagging the -dependency as optional in Maven or using a custom`developmentOnly` configuration in -Gradle (as shown above) is a best practice that prevents devtools from being transitively -applied to other modules that use your project. +special classloader, then it is considered a "`production application`". If that does not +apply to you (i.e. if you run your application from a container), consider excluding +devtools or set the `-Dspring.devtools.restart.enabled=false` system property. + +TIP: Flagging the dependency as optional in Maven or using a custom`developmentOnly` +configuration in Gradle (as shown above) is a best practice that prevents devtools from +being transitively applied to other modules that use your project. TIP: Repackaged archives do not contain devtools by default. If you want to use a <>, you need to disable the