Spring/spring-boot
Spring/spring-boot
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-boot.git synced 2024-08-29 03:06:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch '2.7.x' into main

Browse Source
This commit is contained in:
Madhura Bhave 2022-03-07 21:54:10 -08:00
commit 5960d2dba1
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
spring-boot-project/spring-boot-docs/src/docs/asciidoc/using/devtools.adoc
View File

@ -87,7 +87,8 @@ Note that certain resources, such as static assets and view templates, <<using#u
.Triggering a restart
****
As DevTools monitors classpath resources, the only way to trigger a restart is to update the classpath.
The way in which you cause the classpath to be updated depends on the IDE that you are using:
Whether you're using an IDE or one of the build plugins, the modified files have to be recompiled to trigger a restart.
The way in which you cause the classpath to be updated depends on the tool 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.

5
spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/running.adoc
View File

@ -122,7 +122,10 @@ The preceding example sets the value of the `example` project property to `custo
[[running-your-application.reloading-resources]]
== Reloading Resources
If devtools has been added to your project it will automatically monitor your application for changes.
If devtools has been added to your project it will automatically monitor your application's classpath for changes.
Note that modified files need to be recompiled for the classpath to update inorder to trigger reloading with devtools.
For more details on using devtools, refer to {spring-boot-reference}#using.devtools.restart[this section of the reference documentation].
Alternatively, you can configure `bootRun` such that your application's static resources are loaded from their source location:
[source,groovy,indent=0,subs="verbatim,attributes",role="primary"]