Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify documentation on how to trigger a restart with Dev Tools

Browse Source 
Closes gh-4679
This commit is contained in:
Andy Wilkinson
2015-12-04 14:26:56 +00:00
parent 007ec9e46b
commit 4581853bcc
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
View File

@@ -943,14 +943,13 @@ on the classpath change. This can be a useful feature when working in an IDE as
a very fast feedback loop for code changes. By default, any entry on the classpath that
points to a folder will be monitored for changes.
.Triggering a change
.Triggering a restart
****
As DevTools _only_ monitors classpath resources, the only way to trigger a change is to
update the classpath. On Eclipse, saving is actually updating the project, compiling or
copying resources for you as part of the save action. If you are using IntelliJ IDEA,
there is no such thing as a save action since the resources are saved automatically.
IntelliJ IDEA users should use the `Build` -> `Make Project` action to achieve the same
result.
As DevTools _only_ monitors classpath resources, the only way to trigger a restart is to
update the classpath. In Eclipse, saving a modified file triggers an increment build which
updates the classpath automatically. If you are using IntelliJ IDEA, you will have to
manually run a build using `Build` -> `Make Project`. This will update the classpath and
trigger a restart.
****
NOTE: You can also start your application via the supported build plugins (i.e. Maven and