database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default

database support backs away. If you need to find out what auto-configuration is currently being applied, and why, start your application with the --debug switch. Doing so enables debug logs for a selection Auto-configuration Classes If you find that specific auto-configuration classes that you do not want are being applied, you can use the exclude attribute of @SpringBootApplication to disable them, as shown in the following developmentOnly configuration in Gradle (as shown above) prevents devtools from being transitively applied to other modules that use your project. TIP Repackaged archives do not contain devtools by default