anchor.diff:  ----
   
   NOTE: If you use the Spring Boot starter parent pom, you need to add only the plugin.
  -There is no need to configure it unless you want to change the settings defined in
  -the parent.
  +There is no need to configure it unless you want to change the settings defined in the
  +parent.
   
   
   
  
positive.code: [[using-spring-boot-restart-vs-reload]]
  .Restart vs Reload
  ****
  The restart technology provided by Spring Boot works by using two classloaders.
  Classes that do not change (for example, those from third-party jars) are loaded into a
  _base_ classloader. Classes that you are actively developing are loaded into a _restart_
  classloader. When the application is restarted, the _restart_ classloader is thrown away
  and a new one is created. This approach means that application restarts are typically much
  faster than "`cold starts`", since the _base_ classloader is already available and
  
negative.code: 
  [[using-boot-devtools-restart]]
  === Automatic Restart
  Applications that use `spring-boot-devtools` automatically restart whenever files on the
  classpath change. This can be a useful feature when working in an IDE, as it gives a very
  fast feedback loop for code changes. By default, any entry on the classpath that points to
  a folder is monitored for changes. Note that certain resources, such as static assets and
  view templates, <<using-boot-devtools-restart-exclude, do not need to restart the
  application>>.
  
  .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. In Eclipse, saving a modified file causes the classpath to be updated
  and triggers a restart. In IntelliJ IDEA, building the project (`Build +->+ Make Project`)
  will have the same effect.
  ****
  
  [NOTE]
  ====
  As long as forking is enabled, you can also start your application by using the supported
  build plugins (Maven and Gradle), since DevTools needs an isolated application classloader
  to operate properly. By default, Gradle and Maven do that when they detect DevTools on the
  classpath.
  
  ====
  
  TIP: Automatic restart works very well when used with LiveReload.
  <<using-boot-devtools-livereload,See the LiveReload section>> for details. If you use
  JRebel, automatic restarts are disabled in favor of dynamic class reloading. Other
  devtools features (such as LiveReload and property overrides) can still be used.
  
  NOTE: DevTools relies on the application context's shutdown hook to close it during a
  restart. It does not work correctly if you have disabled the shutdown hook
  