Spring Boot’s flexible packaging options provide a great deal of choice when it comes to deploying your application. Compatibility with the Standard Java “JarFile” From the “spring-boot-actuator-autoconfigure” module From the “spring-boot-autoconfigure” module Generating Your Own Metadata by Using the Annotation Processor Deploying a WAR in an Old (Servlet 2.5) Container Convert an Existing Application to Spring Boot Create a Deployable War File for Older Servlet Containers Build an Executable Archive from Ant without Using spring-boot-antlib Remote Debug a Spring Boot Application Started with Maven Create a Non-executable JAR with Exclusions Extract Specific Libraries When an Executable Jar Runs Use a Spring Boot Application as a Dependency Reload Java Classes without Restarting the Container Reload Templates without Restarting the Container Enable HTTPS When Running behind a Proxy Server Change the AuthenticationManager and Add User Accounts Switch off the Spring Boot Security Configuration Change the HTTP Port or Address of the Actuator Endpoints Execute Liquibase Database Migrations on Startup Execute Flyway Database Migrations on Startup Use a Higher-level Database Migration Tool Configure a Component that is Used by JPA Expose Spring Data Repositories as REST Endpoint Use Spring Data JPA and Mongo Repositories Separate Definitions from Spring Configuration Switch Off the Spring MVC DispatcherServlet Add Servlets, Filters, and Listeners by Using Classpath Scanning

Disable Registration of a Servlet or Filter.

Add a Servlet, Filter, or Listener by Using a Spring Bean Add a Servlet, Filter, or Listener to an Application

Discover Built-in Options for External Properties Change Configuration Depending on the Environment

Change the Location of External Properties of an Application Externalize the Configuration of SpringApplication Automatic Property Expansion Using Gradle Automatically Expand Properties at Build Time Build an ApplicationContext Hierarchy (Adding a Parent or Root Context) Customize the Environment or ApplicationContext Before It Starts Developing Applications with the Groovy Beans DSL

Customizing the Start Script when It Is Written.

Installation as an init.d Service (System V) Phillip Webb, Dave Syer, Josh Long, Stéphane Nicoll, Rob Winch, Andy Wilkinson, Marcel Overdijk, Christian Dupuis, Sébastien Deleuze, Michael Simons, VedranPavić, Jay Bryant, Madhura BhaveĬopies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.

Invalid destination port jar launcher