commit
d131003456
|
@ -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.
|
||||
|
|
|
@ -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"]
|
||||
|
|
Loading…
Reference in New Issue