anchor.diff:  	}
   ----
   
  +CAUTION: Devtools might cause classloading issues, in particular in multi-module projects. <<using#using.devtools.diagnosing-classloading-issues>> explains how to diagnose and solve them.
  +
   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 special classloader, then it is considered a "`production application`".
   You can control this behavior by using the `spring.devtools.restart.enabled` system property.
  
positive.code: If you want to use a <<using#using.devtools.remote-applications,certain remote devtools feature>>, you need to include it.
  When using the Maven plugin, set the `excludeDevtools` property to `false`.
  When using the Gradle plugin, {spring-boot-gradle-plugin-docs}#packaging-executable-configuring-including-development-only-dependencies[configure the task's classpath to include the `developmentOnly` configuration].
  
  
  
  
negative.code: 
  [[using.devtools.restart.customizing-the-classload]]
  ==== Customizing the Restart Classloader
  As described earlier in the <<using-spring-boot-restart-vs-reload>> section, restart functionality is implemented by using two classloaders. If this causes issues, you might need to customize what gets loaded by which classloader.
  
  By default, any open project in your IDE is loaded with the "`restart`" classloader, and any regular `.jar` file is loaded with the "`base`" classloader. The same is true if you use `mvn spring-boot:run` or `gradle bootRun`: The project containing your `@SpringBootApplication` is loaded with the "`restart`" classloader, and everything else with the "`base`" classloader.
  
  You can instruct Spring Boot to load parts of your project with a different classloader by creating a `META-INF/spring-devtools.properties` file.
  The `spring-devtools.properties` file can contain properties prefixed with `restart.exclude` and `restart.include`.
  The `include` elements are items that should be pulled up into the "`restart`" classloader, and the `exclude` elements are items that should be pushed down into the "`base`" classloader.
  The value of the property is a regex pattern that is applied to the classpath, as shown in the following example:
  