The Spring Boot Container allows Spring Boot applications, packaged distZip-style to be run. Note All styles of Spring Boot can be run (e.g. self-executable JAR, WAR file, distZip-style). This is just explicit support for the distZip style.
| Detection Criteria | The lib/spring-boot-.*.jar file exists in either the top-level directory or an immediate subdirectory of the application. |
| Tags | spring-boot=<version> |
The container expects to run the application creating by running gradle distZip in an application built with the Spring Boot Gradle plugin.
If the application uses Spring, Spring profiles can be specified by setting the SPRING_PROFILES_ACTIVE environment variable. This is automatically detected and used by Spring. The Spring Auto-reconfiguration Framework will specify the cloud profile in addition to any others.
The buildpack includes a task process type in the release output using the same command as web, so cf run-task works without an explicit --command.
cf run-task my-app # uses the task process type command
cf run-task my-app --command "..." # explicit overrideTo run a task with a different main class (batch job, migration, etc.), see Java Main Container - CF Tasks.
The Spring Boot Container cannot be configured.