Recommend that DevTools is excluded with custom packaging arrangement

Closes gh-15382
This commit is contained in:
Stephane Nicoll 2019-03-04 15:57:47 +01:00
parent 4f2e788835
commit 4eb73e0050

View File

@ -762,10 +762,13 @@ listings for Maven and Gradle:
NOTE: Developer tools are automatically disabled when running a fully packaged 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 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 special classloader, then it is considered a "`production application`". If that does not
dependency as optional in Maven or using a custom`developmentOnly` configuration in apply to you (i.e. if you run your application from a container), consider excluding
Gradle (as shown above) is a best practice that prevents devtools from being transitively devtools or set the `-Dspring.devtools.restart.enabled=false` system property.
applied to other modules that use your project.
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 TIP: Repackaged archives do not contain devtools by default. If you want to use a
<<using-boot-devtools-remote,certain remote devtools feature>>, you need to disable the <<using-boot-devtools-remote,certain remote devtools feature>>, you need to disable the