fb33610027
Previously, the developmentOnly configuration, typically used for Devtools, had to be declared manually. The BootJar and BootWar tasks then had a property, excludeDevtools, that could be used to control whether or not Devtools would be excluded from the executable archive. This commit updates the reaction to the Java plugin being applied to automatically create the developmentOnly configuration. The classpaths of bootJar and bootWar are then configured not to include the contents of the developmentOnly configuration. As a result of this, the excludeDevtools property is no longer needed and has been deprecated. Its default has also been changed from true to false to make it easy to opt in to Devtools, when configured as a development-only dependency, being included in executable jars and wars by adding developmentOnly to the classpath of the archive task. Closes gh-16599 |
||
|---|---|---|
| .. | ||
| spring-boot | ||
| spring-boot-actuator | ||
| spring-boot-actuator-autoconfigure | ||
| spring-boot-autoconfigure | ||
| spring-boot-cli | ||
| spring-boot-dependencies | ||
| spring-boot-devtools | ||
| spring-boot-docs | ||
| spring-boot-parent | ||
| spring-boot-properties-migrator | ||
| spring-boot-starters | ||
| spring-boot-test | ||
| spring-boot-test-autoconfigure | ||
| spring-boot-tools | ||