diff --git "a/Spring-Boot/version/documents/2.0.0.M3/\345\217\202\350\200\203\346\211\213\345\206\214.md" "b/Spring-Boot/version/documents/2.0.0.M3/\345\217\202\350\200\203\346\211\213\345\206\214.md"
new file mode 100644
index 0000000000000000000000000000000000000000..eda3d9c9aece75a1fbfbb04c63922f27582aac02
--- /dev/null
+++ "b/Spring-Boot/version/documents/2.0.0.M3/\345\217\202\350\200\203\346\211\213\345\206\214.md"
@@ -0,0 +1,14283 @@
+# Spring Boot Reference Guide
+
+### [英文文档](guide.md)
+
+## Authors
+
+Phillip Webb, Dave Syer, Josh Long, Stéphane Nicoll, Rob Winch, Andy Wilkinson, Marcel Overdijk, Christian Dupuis, Sébastien Deleuze, Michael Simons, Vedran Pavić
+
+**2.0.0.M3**
+
+Copyright © 2012-2017
+
+*Copies 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.*
+
+------
+
+**Table of Contents**
+
+- [I. Spring Boot Documentation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-documentation)
+
+ - [1. About the documentation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-documentation-about)
+ - [2. Getting help](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-documentation-getting-help)
+ - [3. First steps](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-documentation-first-steps)
+ - [4. Working with Spring Boot](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_working_with_spring_boot)
+ - [5. Learning about Spring Boot features](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_learning_about_spring_boot_features)
+ - [6. Moving to production](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_moving_to_production)
+ - [7. Advanced topics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_advanced_topics)
+
+- [II. Getting started](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started)
+
+ - [8. Introducing Spring Boot](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-introducing-spring-boot)
+ - [9. System Requirements](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-system-requirements)
+ - [9.1. Servlet containers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-system-requirements-servlet-containers)
+ - [10. Installing Spring Boot](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-installing-spring-boot)
+ - [10.1. Installation instructions for the Java developer](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-installation-instructions-for-java)
+ - [10.1.1. Maven installation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-maven-installation)
+ - [10.1.2. Gradle installation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-gradle-installation)
+ - [10.2. Installing the Spring Boot CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-installing-the-cli)
+ - [10.2.1. Manual installation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-manual-cli-installation)
+ - [10.2.2. Installation with SDKMAN!](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-sdkman-cli-installation)
+ - [10.2.3. OSX Homebrew installation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-homebrew-cli-installation)
+ - [10.2.4. MacPorts installation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-macports-cli-installation)
+ - [10.2.5. Command-line completion](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-cli-command-line-completion)
+ - [10.2.6. Quick start Spring CLI example](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-cli-example)
+ - [10.3. Upgrading from an earlier version of Spring Boot](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-upgrading-from-an-earlier-version)
+ - [11. Developing your first Spring Boot application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application)
+ - [11.1. Creating the POM](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-pom)
+ - [11.2. Adding classpath dependencies](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-dependencies)
+ - [11.3. Writing the code](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-code)
+ - [11.3.1. The @RestController and @RequestMapping annotations](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-annotations)
+ - [11.3.2. The @EnableAutoConfiguration annotation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-auto-configuration)
+ - [11.3.3. The “main” method](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-main-method)
+ - [11.4. Running the example](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-run)
+ - [11.5. Creating an executable jar](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-executable-jar)
+ - [12. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-whats-next)
+
+- [III. Using Spring Boot](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot)
+
+ - [13. Build systems](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-build-systems)
+ - [13.1. Dependency management](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-dependency-management)
+ - [13.2. Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven)
+ - [13.2.1. Inheriting the starter parent](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven-parent-pom)
+ - [13.2.2. Using Spring Boot without the parent POM](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven-without-a-parent)
+ - [13.2.3. Using the Spring Boot Maven plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven-plugin)
+ - [13.3. Gradle](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-gradle)
+ - [13.4. Ant](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-ant)
+ - [13.5. Starters](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-starter)
+ - [14. Structuring your code](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-structuring-your-code)
+ - [14.1. Using the “default” package](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-using-the-default-package)
+ - [14.2. Locating the main application class](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-locating-the-main-class)
+ - [15. Configuration classes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-configuration-classes)
+ - [15.1. Importing additional configuration classes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-importing-configuration)
+ - [15.2. Importing XML configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-importing-xml-configuration)
+ - [16. Auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-auto-configuration)
+ - [16.1. Gradually replacing auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-replacing-auto-configuration)
+ - [16.2. Disabling specific auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-disabling-specific-auto-configuration)
+ - [17. Spring Beans and dependency injection](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-spring-beans-and-dependency-injection)
+ - [18. Using the @SpringBootApplication annotation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-using-springbootapplication-annotation)
+ - [19. Running your application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-your-application)
+ - [19.1. Running from an IDE](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-from-an-ide)
+ - [19.2. Running as a packaged application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-as-a-packaged-application)
+ - [19.3. Using the Maven plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-with-the-maven-plugin)
+ - [19.4. Using the Gradle plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-with-the-gradle-plugin)
+ - [19.5. Hot swapping](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-hot-swapping)
+ - [20. Developer tools](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools)
+ - [20.1. Property defaults](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-property-defaults)
+ - [20.2. Automatic restart](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart)
+ - [20.2.1. Excluding resources](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-exclude)
+ - [20.2.2. Watching additional paths](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-additional-paths)
+ - [20.2.3. Disabling restart](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-disable)
+ - [20.2.4. Using a trigger file](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-triggerfile)
+ - [20.2.5. Customizing the restart classloader](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-customizing-classload)
+ - [20.2.6. Known limitations](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-known-restart-limitations)
+ - [20.3. LiveReload](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-livereload)
+ - [20.4. Global settings](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-globalsettings)
+ - [20.5. Remote applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-remote)
+ - [20.5.1. Running the remote client application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_running_the_remote_client_application)
+ - [20.5.2. Remote update](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-remote-update)
+ - [21. Packaging your application for production](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-packaging-for-production)
+ - [22. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-whats-next)
+
+- [IV. Spring Boot features](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features)
+
+ - [23. SpringApplication](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-application)
+ - [23.1. Startup failure](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_startup_failure)
+ - [23.2. Customizing the Banner](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-banner)
+ - [23.3. Customizing SpringApplication](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-customizing-spring-application)
+ - [23.4. Fluent builder API](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-fluent-builder-api)
+ - [23.5. Application events and listeners](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-application-events-and-listeners)
+ - [23.6. Web environment](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-web-environment)
+ - [23.7. Accessing application arguments](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-application-arguments)
+ - [23.8. Using the ApplicationRunner or CommandLineRunner](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-command-line-runner)
+ - [23.9. Application exit](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-application-exit)
+ - [23.10. Admin features](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-application-admin)
+ - [24. Externalized Configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config)
+ - [24.1. Configuring random values](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-random-values)
+ - [24.2. Accessing command line properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-command-line-args)
+ - [24.3. Application property files](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-application-property-files)
+ - [24.4. Profile-specific properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-profile-specific-properties)
+ - [24.5. Placeholders in properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-placeholders-in-properties)
+ - [24.6. Using YAML instead of Properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-yaml)
+ - [24.6.1. Loading YAML](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-loading-yaml)
+ - [24.6.2. Exposing YAML as properties in the Spring Environment](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-exposing-yaml-to-spring)
+ - [24.6.3. Multi-profile YAML documents](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-multi-profile-yaml)
+ - [24.6.4. YAML shortcomings](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-yaml-shortcomings)
+ - [24.6.5. Merging YAML lists](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-complex-type-merge)
+ - [24.7. Type-safe Configuration Properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-typesafe-configuration-properties)
+ - [24.7.1. Third-party configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-3rd-party-configuration)
+ - [24.7.2. Relaxed binding](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-relaxed-binding)
+ - [24.7.3. Properties conversion](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-conversion)
+ - [24.7.4. @ConfigurationProperties Validation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-validation)
+ - [24.7.5. @ConfigurationProperties vs. @Value](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-vs-value)
+ - [25. Profiles](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-profiles)
+ - [25.1. Adding active profiles](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-adding-active-profiles)
+ - [25.2. Programmatically setting profiles](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-programmatically-setting-profiles)
+ - [25.3. Profile-specific configuration files](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-profile-specific-configuration)
+ - [26. Logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logging)
+ - [26.1. Log format](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logging-format)
+ - [26.2. Console output](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logging-console-output)
+ - [26.2.1. Color-coded output](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logging-color-coded-output)
+ - [26.3. File output](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logging-file-output)
+ - [26.4. Log Levels](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-log-levels)
+ - [26.5. Custom log configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-log-configuration)
+ - [26.6. Logback extensions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logback-extensions)
+ - [26.6.1. Profile-specific configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_profile_specific_configuration)
+ - [26.6.2. Environment properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_environment_properties)
+ - [27. Developing web applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-developing-web-applications)
+ - [27.1. The ‘Spring Web MVC framework’](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc)
+ - [27.1.1. Spring MVC auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-auto-configuration)
+ - [27.1.2. HttpMessageConverters](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-message-converters)
+ - [27.1.3. Custom JSON Serializers and Deserializers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-json-components)
+ - [27.1.4. MessageCodesResolver](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-message-codes)
+ - [27.1.5. Static Content](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-static-content)
+ - [27.1.6. Custom Favicon](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-favicon)
+ - [27.1.7. ConfigurableWebBindingInitializer](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-web-binding-initializer)
+ - [27.1.8. Template engines](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-template-engines)
+ - [27.1.9. Error Handling](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-error-handling)
+ - [Custom error pages](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-error-handling-custom-error-pages)
+ - [Mapping error pages outside of Spring MVC](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-error-handling-mapping-error-pages-without-mvc)
+ - [Error Handling on WebSphere Application Server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-error-handling-websphere)
+ - [27.1.10. Spring HATEOAS](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-hateoas)
+ - [27.1.11. CORS support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-cors)
+ - [27.2. The ‘Spring WebFlux framework’](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-webflux)
+ - [27.2.1. Spring WebFlux auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-webflux-auto-configuration)
+ - [27.2.2. HTTP codecs with HttpMessageReaders and HttpMessageWriters](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-webflux-httpcodecs)
+ - [27.2.3. Static Content](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-webflux-static-content)
+ - [27.2.4. Template engines](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-webflux-template-engines)
+ - [27.3. JAX-RS and Jersey](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jersey)
+ - [27.4. Embedded servlet container support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container)
+ - [27.4.1. Servlets, Filters, and listeners](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container-servlets-filters-listeners)
+ - [Registering Servlets, Filters, and listeners as Spring beans](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container-servlets-filters-listeners-beans)
+ - [27.4.2. Servlet Context Initialization](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container-context-initializer)
+ - [Scanning for Servlets, Filters, and listeners](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container-servlets-filters-listeners-scanning)
+ - [27.4.3. The ServletWebServerApplicationContext](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container-application-context)
+ - [27.4.4. Customizing embedded servlet containers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-customizing-embedded-containers)
+ - [Programmatic customization](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-programmatic-embedded-container-customization)
+ - [Customizing ConfigurableServletWebServerFactory directly](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-customizing-configurableservletwebserverfactory-directly)
+ - [27.4.5. JSP limitations](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jsp-limitations)
+ - [28. Security](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security)
+ - [28.1. OAuth2](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-oauth2)
+ - [28.1.1. Authorization Server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-oauth2-authorization-server)
+ - [28.1.2. Resource Server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-oauth2-resource-server)
+ - [28.2. Token Type in User Info](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-oauth2-token-type)
+ - [28.3. Customizing the User Info RestTemplate](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-custom-user-info)
+ - [28.3.1. Client](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-custom-user-info-client)
+ - [28.3.2. Single Sign On](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-oauth2-single-sign-on)
+ - [28.4. Actuator Security](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-security-actuator)
+ - [29. Working with SQL databases](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-sql)
+ - [29.1. Configure a DataSource](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-configure-datasource)
+ - [29.1.1. Embedded Database Support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-database-support)
+ - [29.1.2. Connection to a production database](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connect-to-production-database)
+ - [29.1.3. Connection to a JNDI DataSource](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-a-jndi-datasource)
+ - [29.2. Using JdbcTemplate](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-using-jdbc-template)
+ - [29.3. JPA and ‘Spring Data’](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jpa-and-spring-data)
+ - [29.3.1. Entity Classes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-entity-classes)
+ - [29.3.2. Spring Data JPA Repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-jpa-repositories)
+ - [29.3.3. Creating and dropping JPA databases](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-creating-and-dropping-jpa-databases)
+ - [29.3.4. Open EntityManager in View](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jpa-in-web-environment)
+ - [29.4. Using H2’s web console](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-sql-h2-console)
+ - [29.4.1. Changing the H2 console’s path](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-sql-h2-console-custom-path)
+ - [29.4.2. Securing the H2 console](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-sql-h2-console-securing)
+ - [29.5. Using jOOQ](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jooq)
+ - [29.5.1. Code Generation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_code_generation)
+ - [29.5.2. Using DSLContext](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_using_dslcontext)
+ - [29.5.3. jOOQ SQL dialect](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_jooq_sql_dialect)
+ - [29.5.4. Customizing jOOQ](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_customizing_jooq)
+ - [30. Working with NoSQL technologies](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-nosql)
+ - [30.1. Redis](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-redis)
+ - [30.1.1. Connecting to Redis](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-redis)
+ - [30.2. MongoDB](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-mongodb)
+ - [30.2.1. Connecting to a MongoDB database](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-mongodb)
+ - [30.2.2. MongoTemplate](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-mongo-template)
+ - [30.2.3. Spring Data MongoDB repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-mongo-repositories)
+ - [30.2.4. Embedded Mongo](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-mongo-embedded)
+ - [30.3. Neo4j](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-neo4j)
+ - [30.3.1. Connecting to a Neo4j database](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-neo4j)
+ - [30.3.2. Using the embedded mode](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-neo4j-embedded)
+ - [30.3.3. Neo4jSession](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-neo4j-ogm-session)
+ - [30.3.4. Spring Data Neo4j repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-neo4j-repositories)
+ - [30.3.5. Repository example](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_repository_example)
+ - [30.4. Gemfire](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-gemfire)
+ - [30.5. Solr](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-solr)
+ - [30.5.1. Connecting to Solr](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-solr)
+ - [30.5.2. Spring Data Solr repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-solr-repositories)
+ - [30.6. Elasticsearch](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-elasticsearch)
+ - [30.6.1. Connecting to Elasticsearch using Jest](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-elasticsearch-jest)
+ - [30.6.2. Connecting to Elasticsearch using Spring Data](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-elasticsearch-spring-data)
+ - [30.6.3. Spring Data Elasticsearch repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-elasticsearch-repositories)
+ - [30.7. Cassandra](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-cassandra)
+ - [30.7.1. Connecting to Cassandra](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-cassandra)
+ - [30.7.2. Spring Data Cassandra repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-cassandra-repositories)
+ - [30.8. Couchbase](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-couchbase)
+ - [30.8.1. Connecting to Couchbase](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-couchbase)
+ - [30.8.2. Spring Data Couchbase repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-data-couchbase-repositories)
+ - [30.9. LDAP](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-ldap)
+ - [30.9.1. Connecting to an LDAP server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-ldap-connecting)
+ - [30.9.2. Spring Data LDAP repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-ldap-spring-data-repositories)
+ - [30.9.3. Embedded in-memory LDAP server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-ldap-embedded)
+ - [30.10. InfluxDB](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-influxdb)
+ - [30.10.1. Connecting to InfluxDB](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-connecting-to-influxdb)
+ - [31. Caching](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching)
+ - [31.1. Supported cache providers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_supported_cache_providers)
+ - [31.1.1. Generic](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-generic)
+ - [31.1.2. JCache (JSR-107)](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-jcache)
+ - [31.1.3. EhCache 2.x](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-ehcache2)
+ - [31.1.4. Hazelcast](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-hazelcast)
+ - [31.1.5. Infinispan](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-infinispan)
+ - [31.1.6. Couchbase](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-couchbase)
+ - [31.1.7. Redis](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-redis)
+ - [31.1.8. Caffeine](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-caffeine)
+ - [31.1.9. Simple](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-simple)
+ - [31.1.10. None](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-caching-provider-none)
+ - [32. Messaging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-messaging)
+ - [32.1. JMS](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jms)
+ - [32.1.1. ActiveMQ support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-activemq)
+ - [32.1.2. Artemis support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-artemis)
+ - [32.1.3. Using a JNDI ConnectionFactory](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jms-jndi)
+ - [32.1.4. Sending a message](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-using-jms-sending)
+ - [32.1.5. Receiving a message](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-using-jms-receiving)
+ - [32.2. AMQP](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-amqp)
+ - [32.2.1. RabbitMQ support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-rabbitmq)
+ - [32.2.2. Sending a message](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-using-amqp-sending)
+ - [32.2.3. Receiving a message](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-using-amqp-receiving)
+ - [32.3. Apache Kafka Support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-kafka)
+ - [32.3.1. Sending a Message](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-kafka-sending-a-message)
+ - [32.3.2. Receiving a Message](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-kafka-receiving-a-message)
+ - [32.3.3. Additional Kafka Properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-kafka-extra-props)
+ - [33. Calling REST services with ‘RestTemplate’](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-resttemplate)
+ - [33.1. RestTemplate customization](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-resttemplate-customization)
+ - [34. Calling REST services with ‘WebClient’](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-webclient)
+ - [34.1. WebClient customization](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-webclient-customization)
+ - [35. Validation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-validation)
+ - [36. Sending email](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-email)
+ - [37. Distributed Transactions with JTA](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta)
+ - [37.1. Using an Atomikos transaction manager](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta-atomikos)
+ - [37.2. Using a Bitronix transaction manager](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta-bitronix)
+ - [37.3. Using a Narayana transaction manager](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta-narayana)
+ - [37.4. Using a Java EE managed transaction manager](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta-javaee)
+ - [37.5. Mixing XA and non-XA JMS connections](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta-mixed-jms)
+ - [37.6. Supporting an alternative embedded transaction manager](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jta-supporting-alternative-embedded)
+ - [38. Hazelcast](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-hazelcast)
+ - [39. Quartz Scheduler](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-quartz)
+ - [40. Spring Integration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-integration)
+ - [41. Spring Session](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-session)
+ - [42. Monitoring and management over JMX](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jmx)
+ - [43. Testing](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing)[43.1. Test scope dependencies](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-test-scope-dependencies)
+ - [43.2. Testing Spring applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-applications)
+ - [43.3. Testing Spring Boot applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications)
+ - [43.3.1. Detecting test configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-detecting-config)
+ - [43.3.2. Excluding test configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-excluding-config)
+ - [43.3.3. Working with random ports](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-working-with-random-ports)
+ - [43.3.4. Mocking and spying beans](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-mocking-beans)
+ - [43.3.5. Auto-configured tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-tests)
+ - [43.3.6. Auto-configured JSON tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-json-tests)
+ - [43.3.7. Auto-configured Spring MVC tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-mvc-tests)
+ - [43.3.8. Auto-configured Spring WebFlux tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-webflux-tests)
+ - [43.3.9. Auto-configured Data JPA tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-jpa-test)
+ - [43.3.10. Auto-configured JDBC tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-jdbc-test)
+ - [43.3.11. Auto-configured jOOQ tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-jooq-test)
+ - [43.3.12. Auto-configured Data MongoDB tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-mongo-test)
+ - [43.3.13. Auto-configured Data Neo4j tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-neo4j-test)
+ - [43.3.14. Auto-configured Data Redis tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-redis-test)
+ - [43.3.15. Auto-configured Data LDAP tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-ldap-test)
+ - [43.3.16. Auto-configured REST clients](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-rest-client)
+ - [43.3.17. Auto-configured Spring REST Docs tests](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-testing-autoconfigured-rest-docs)
+ - [43.3.18. Using Spock to test Spring Boot applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications-with-spock)
+ - [43.4. Test utilities](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-test-utilities)
+ - [43.4.1. ConfigFileApplicationContextInitializer](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-configfileapplicationcontextinitializer-test-utility)
+ - [43.4.2. EnvironmentTestUtils](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-environment-test-utilities)
+ - [43.4.3. OutputCapture](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-output-capture-test-utility)
+ - [43.4.4. TestRestTemplate](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-rest-templates-test-utility)
+ - [44. WebSockets](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-websockets)
+ - [45. Web Services](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-webservices)
+ - [46. Creating your own auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-developing-auto-configuration)
+ - [46.1. Understanding auto-configured beans](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-understanding-auto-configured-beans)
+ - [46.2. Locating auto-configuration candidates](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-locating-auto-configuration-candidates)
+ - [46.3. Condition annotations](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-condition-annotations)
+ - [46.3.1. Class conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-class-conditions)
+ - [46.3.2. Bean conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-bean-conditions)
+ - [46.3.3. Property conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-property-conditions)
+ - [46.3.4. Resource conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-resource-conditions)
+ - [46.3.5. Web application conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-web-application-conditions)
+ - [46.3.6. SpEL expression conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spel-conditions)
+ - [46.4. Creating your own starter](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-starter)
+ - [46.4.1. Naming](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-starter-naming)
+ - [46.4.2. Autoconfigure module](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-starter-module-autoconfigure)
+ - [46.4.3. Starter module](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-starter-module-starter)
+ - [47. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-whats-next)
+
+- [V. Spring Boot Actuator: Production-ready features](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready)
+
+ - [48. Enabling production-ready features](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-enabling)
+ - [49. Endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-endpoints)
+ - [49.1. Customizing endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-endpoints)
+ - [49.2. Hypermedia for actuator MVC endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-endpoint-hypermedia)
+ - [49.3. CORS support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-endpoint-cors)
+ - [49.4. Adding custom endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-endpoints-programmatically)
+ - [49.5. Health information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-health)
+ - [49.6. Security with HealthIndicators](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_security_with_healthindicators)
+ - [49.6.1. Auto-configured HealthIndicators](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_auto_configured_healthindicators)
+ - [49.6.2. Writing custom HealthIndicators](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_writing_custom_healthindicators)
+ - [49.7. Application information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-application-info)
+ - [49.7.1. Auto-configured InfoContributors](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-application-info-autoconfigure)
+ - [49.7.2. Custom application info information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-application-info-env)
+ - [49.7.3. Git commit information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-application-info-git)
+ - [49.7.4. Build information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-application-info-build)
+ - [49.7.5. Writing custom InfoContributors](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-application-info-custom)
+ - [50. Monitoring and management over HTTP](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-monitoring)
+ - [50.1. Accessing sensitive endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-sensitive-endpoints)
+ - [50.2. Customizing the management endpoint paths](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-management-server-context-path)
+ - [50.3. Customizing the management server port](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-management-server-port)
+ - [50.4. Configuring management-specific SSL](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-management-specific-ssl)
+ - [50.5. Customizing the management server address](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-management-server-address)
+ - [50.6. Disabling HTTP endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-disabling-http-endpoints)
+ - [50.7. HTTP health endpoint format and access restrictions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-health-access-restrictions)
+ - [51. Monitoring and management over JMX](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-jmx)
+ - [51.1. Customizing MBean names](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-custom-mbean-names)
+ - [51.2. Disabling JMX endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-disable-jmx-endpoints)
+ - [51.3. Using Jolokia for JMX over HTTP](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-jolokia)
+ - [51.3.1. Customizing Jolokia](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-jolokia)
+ - [51.3.2. Disabling Jolokia](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-disabling-jolokia)
+ - [52. Loggers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-loggers)
+ - [52.1. Configure a Logger](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-logger-configuration)
+ - [53. Metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metrics)
+ - [53.1. System metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-system-metrics)
+ - [53.2. DataSource metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-datasource-metrics)
+ - [53.3. Cache metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-datasource-cache)
+ - [53.4. Tomcat session metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-session-metrics)
+ - [53.5. Recording your own metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-recording-metrics)
+ - [53.6. Adding your own public metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-public-metrics)
+ - [53.7. Metric writers, exporters and aggregation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metric-writers)
+ - [53.7.1. Example: Export to Redis](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metric-writers-export-to-redis)
+ - [53.7.2. Example: Export to Open TSDB](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metric-writers-export-to-open-tsdb)
+ - [53.7.3. Example: Export to Statsd](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metric-writers-export-to-statsd)
+ - [53.7.4. Example: Export to JMX](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metric-writers-export-to-jmx)
+ - [53.8. Aggregating metrics from multiple sources](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metric-aggregation)
+ - [53.9. Dropwizard Metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-dropwizard-metrics)
+ - [53.10. Message channel integration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metrics-message-channel-integration)
+ - [54. Auditing](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-auditing)
+ - [55. Tracing](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-tracing)
+ - [55.1. Custom tracing](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-custom-tracing)
+ - [56. Process monitoring](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-process-monitoring)
+ - [56.1. Extend configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-process-monitoring-configuration)
+ - [56.2. Programmatically](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-process-monitoring-programmatically)
+ - [57. Cloud Foundry support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-cloudfoundry)
+ - [57.1. Disabling extended Cloud Foundry actuator support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-cloudfoundry-disable)
+ - [57.2. Cloud Foundry self signed certificates](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-cloudfoundry-ssl)
+ - [57.3. Custom security configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-cloudfoundry-custom-security)
+ - [58. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-whats-next)
+
+- [VI. Deploying Spring Boot applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment)
+
+ - [59. Deploying to the cloud](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment)
+ - [59.1. Cloud Foundry](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-cloud-foundry)
+ - [59.1.1. Binding to services](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-cloud-foundry-services)
+ - [59.2. Heroku](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-heroku)
+ - [59.3. OpenShift](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-openshift)
+ - [59.4. Amazon Web Services (AWS)](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-aws)
+ - [59.4.1. AWS Elastic Beanstalk](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_aws_elastic_beanstalk)
+ - [Using the Tomcat platform](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_using_the_tomcat_platform)
+ - [Using the Java SE platform](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_using_the_java_se_platform)
+ - [Best practices](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_best_practices)
+ - [59.4.2. Summary](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_summary)
+ - [59.5. Boxfuse and Amazon Web Services](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-boxfuse)
+ - [59.6. Google Cloud](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment-gae)
+ - [60. Installing Spring Boot applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-install)
+ - [60.1. Supported operating systems](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-install-supported-operating-systems)
+ - [60.2. Unix/Linux services](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-service)
+ - [60.2.1. Installation as an init.d service (System V)](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-initd-service)
+ - [Securing an init.d service](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-initd-service-securing)
+ - [60.2.2. Installation as a systemd service](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-systemd-service)
+ - [60.2.3. Customizing the startup script](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-script-customization)
+ - [Customizing script when it’s written](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-script-customization-when-it-written)
+ - [Customizing script when it runs](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-script-customization-when-it-runs)
+ - [60.3. Microsoft Windows services](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-windows)
+ - [61. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-whats-next)
+
+- [VII. Spring Boot CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli)
+
+ - [62. Installing the CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-installation)
+ - [63. Using the CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-using-the-cli)
+ - [63.1. Running applications using the CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-run)
+ - [63.1.1. Deduced “grab” dependencies](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-deduced-grab-annotations)
+ - [63.1.2. Deduced “grab” coordinates](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-default-grab-deduced-coordinates)
+ - [63.1.3. Default import statements](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-default-import-statements)
+ - [63.1.4. Automatic main method](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-automatic-main-method)
+ - [63.1.5. Custom dependency management](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-default-grab-deduced-coordinates-custom-dependency-management)
+ - [63.2. Applications with multiple source files](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-multiple-source-files)
+ - [63.3. Packaging your application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-jar)
+ - [63.4. Initialize a new project](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-init)
+ - [63.5. Using the embedded shell](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-shell)
+ - [63.6. Adding extensions to the CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-install-uninstall)
+ - [64. Developing application with the Groovy beans DSL](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-groovy-beans-dsl)
+ - [65. Configuring the CLI with settings.xml](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-maven-settings)
+ - [66. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli-whats-next)
+
+- [VIII. Build tool plugins](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins)
+
+ - [67. Spring Boot Maven plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-maven-plugin)
+ - [67.1. Including the plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-include-maven-plugin)
+ - [67.2. Packaging executable jar and war files](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-maven-packaging)
+ - [68. Spring Boot Gradle plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-gradle-plugin)
+ - [69. Spring Boot AntLib module](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-antlib)
+ - [69.1. Spring Boot Ant tasks](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_spring_boot_ant_tasks)
+ - [69.1.1. spring-boot:exejar](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_spring_boot_exejar)
+ - [69.1.2. Examples](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_examples)
+ - [69.2. spring-boot:findmainclass](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_spring_boot_findmainclass)
+ - [69.2.1. Examples](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_examples_2)
+ - [70. Supporting other build systems](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-other-build-systems)
+ - [70.1. Repackaging archives](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-repackaging-archives)
+ - [70.2. Nested libraries](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-nested-libraries)
+ - [70.3. Finding a main class](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-find-a-main-class)
+ - [70.4. Example repackage implementation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-repackage-implementation)[71. What to read next](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-whats-next)
+
+- [IX. ‘How-to’ guides](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto)
+
+ - [72. Spring Boot application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-spring-boot-application)
+ - [72.1. Create your own FailureAnalyzer](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-failure-analyzer)
+ - [72.2. Troubleshoot auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-troubleshoot-auto-configuration)
+ - [72.3. Customize the Environment or ApplicationContext before it starts](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-the-environment-or-application-context)
+ - [72.4. Build an ApplicationContext hierarchy (adding a parent or root context)](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-build-an-application-context-hierarchy)
+ - [72.5. Create a non-web application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-a-non-web-application)
+ - [73. Properties & configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-properties-and-configuration)
+ - [73.1. Automatically expand properties at build time](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-automatic-expansion)
+ - [73.1.1. Automatic property expansion using Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-automatic-expansion-maven)
+ - [73.1.2. Automatic property expansion using Gradle](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-automatic-expansion-gradle)
+ - [73.2. Externalize the configuration of SpringApplication](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-externalize-configuration)
+ - [73.3. Change the location of external properties of an application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-change-the-location-of-external-properties)
+ - [73.4. Use ‘short’ command line arguments](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-short-command-line-arguments)
+ - [73.5. Use YAML for external properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-yaml-for-external-properties)
+ - [73.6. Set the active Spring profiles](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-set-active-spring-profiles)
+ - [73.7. Change configuration depending on the environment](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-change-configuration-depending-on-the-environment)
+ - [73.8. Discover built-in options for external properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-discover-build-in-options-for-external-properties)
+ - [74. Embedded Web servers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-embedded-web-servers)
+ - [74.1. Use another Web server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-another-web-server)
+ - [74.2. Configure Jetty](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-jetty)
+ - [74.3. Add a Servlet, Filter or Listener to an application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-add-a-servlet-filter-or-listener)
+ - [74.3.1. Add a Servlet, Filter or Listener using a Spring bean](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-add-a-servlet-filter-or-listener-as-spring-bean)
+ - [Disable registration of a Servlet or Filter](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-disable-registration-of-a-servlet-or-filter)
+ - [74.3.2. Add Servlets, Filters, and Listeners using classpath scanning](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-add-a-servlet-filter-or-listener-using-scanning)
+ - [74.4. Change the HTTP port](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-change-the-http-port)
+ - [74.5. Use a random unassigned HTTP port](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-user-a-random-unassigned-http-port)
+ - [74.6. Discover the HTTP port at runtime](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-discover-the-http-port-at-runtime)
+ - [74.7. Configure SSL](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-ssl)
+ - [74.8. Configure Access Logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-accesslogs)
+ - [74.9. Use behind a front-end proxy server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-tomcat-behind-a-proxy-server)
+ - [74.9.1. Customize Tomcat’s proxy configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-tomcat-behind-a-proxy-server)
+ - [74.10. Configure Tomcat](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-tomcat)
+ - [74.11. Enable Multiple Connectors with Tomcat](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-enable-multiple-connectors-in-tomcat)
+ - [74.12. Use Tomcat’s LegacyCookieProcessor](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-tomcat-legacycookieprocessor)
+ - [74.13. Configure Undertow](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-undertow)
+ - [74.14. Enable Multiple Listeners with Undertow](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-enable-multiple-listeners-in-undertow)
+ - [74.15. Create WebSocket endpoints using @ServerEndpoint](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-websocket-endpoints-using-serverendpoint)
+ - [74.16. Enable HTTP response compression](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#how-to-enable-http-response-compression)
+ - [75. Spring MVC](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-spring-mvc)
+ - [75.1. Write a JSON REST service](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-write-a-json-rest-service)
+ - [75.2. Write an XML REST service](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-write-an-xml-rest-service)
+ - [75.3. Customize the Jackson ObjectMapper](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-the-jackson-objectmapper)
+ - [75.4. Customize the @ResponseBody rendering](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-the-responsebody-rendering)
+ - [75.5. Handling Multipart File Uploads](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-multipart-file-upload-configuration)
+ - [75.6. Switch off the Spring MVC DispatcherServlet](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-switch-off-the-spring-mvc-dispatcherservlet)
+ - [75.7. Switch off the Default MVC configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-switch-off-default-mvc-configuration)
+ - [75.8. Customize ViewResolvers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-view-resolvers)
+ - [76. HTTP clients](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-http-clients)
+ - [76.1. Configure RestTemplate to use a proxy](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-http-clients-proxy-configuration)
+ - [77. Logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-logging)
+ - [77.1. Configure Logback for logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-logback-for-logging)
+ - [77.1.1. Configure logback for file only output](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-logback-for-logging-fileonly)
+ - [77.2. Configure Log4j for logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-log4j-for-logging)
+ - [77.2.1. Use YAML or JSON to configure Log4j 2](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-log4j-for-logging-yaml-or-json-config)
+ - [78. Data Access](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-data-access)
+ - [78.1. Configure a custom DataSource](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-a-datasource)
+ - [78.2. Configure Two DataSources](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-two-datasources)
+ - [78.3. Use Spring Data repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-spring-data-repositories)
+ - [78.4. Separate @Entity definitions from Spring configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-separate-entity-definitions-from-spring-configuration)
+ - [78.5. Configure JPA properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-jpa-properties)
+ - [78.6. Configure Hibernate Naming Strategy](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-hibernate-naming-strategy)
+ - [78.7. Use a custom EntityManagerFactory](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-custom-entity-manager)
+ - [78.8. Use Two EntityManagers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-two-entity-managers)
+ - [78.9. Use a traditional persistence.xml](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-traditional-persistence-xml)
+ - [78.10. Use Spring Data JPA and Mongo repositories](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-spring-data-jpa--and-mongo-repositories)
+ - [78.11. Expose Spring Data repositories as REST endpoint](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-exposing-spring-data-repositories-rest-endpoint)
+ - [78.12. Configure a component that is used by JPA](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-configure-a-component-that-is-used-by-JPA)
+ - [79. Database initialization](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-database-initialization)
+ - [79.1. Initialize a database using JPA](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-initialize-a-database-using-jpa)
+ - [79.2. Initialize a database using Hibernate](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-initialize-a-database-using-hibernate)
+ - [79.3. Initialize a database using Spring JDBC](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-initialize-a-database-using-spring-jdbc)
+ - [79.4. Initialize a Spring Batch database](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-initialize-a-spring-batch-database)
+ - [79.5. Use a higher-level database migration tool](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-a-higher-level-database-migration-tool)
+ - [79.5.1. Execute Flyway database migrations on startup](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-execute-flyway-database-migrations-on-startup)
+ - [79.5.2. Execute Liquibase database migrations on startup](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-execute-liquibase-database-migrations-on-startup)
+ - [80. Messaging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-messaging)
+ - [80.1. Disable transacted JMS session](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-jms-disable-transaction)
+ - [81. Batch applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-batch-applications)
+ - [81.1. Execute Spring Batch jobs on startup](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-execute-spring-batch-jobs-on-startup)
+ - [82. Actuator](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-actuator)
+ - [82.1. Change the HTTP port or address of the actuator endpoints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-change-the-http-port-or-address-of-the-actuator-endpoints)
+ - [82.2. Customize the ‘whitelabel’ error page](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-the-whitelabel-error-page)
+ - [82.3. Actuator and Jersey](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-actuator-with-jersey)
+ - [83. Security](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-security)
+ - [83.1. Switch off the Spring Boot security configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-switch-off-spring-boot-security-configuration)
+ - [83.2. Change the AuthenticationManager and add user accounts](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-change-the-authenticationmanager-and-add-user-accounts)
+ - [83.3. Enable HTTPS when running behind a proxy server](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-enable-https)
+ - [84. Hot swapping](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-hotswapping)
+ - [84.1. Reload static content](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-static-content)
+ - [84.2. Reload templates without restarting the container](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-thymeleaf-template-content)
+ - [84.2.1. Thymeleaf templates](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-thymeleaf-content)
+ - [84.2.2. FreeMarker templates](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-freemarker-content)
+ - [84.2.3. Groovy templates](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-groovy-template-content)
+ - [84.3. Fast application restarts](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-fast-restart)
+ - [84.4. Reload Java classes without restarting the container](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-reload-java-classes-without-restarting)
+ - [85. Build](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-build)
+ - [85.1. Generate build information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-build-info)
+ - [85.2. Generate git information](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-git-info)
+ - [85.3. Customize dependency versions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-customize-dependency-versions)
+ - [85.4. Create an executable JAR with Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-an-executable-jar-with-maven)
+ - [85.5. Use a Spring Boot application as a dependency](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-an-additional-executable-jar)
+ - [85.6. Extract specific libraries when an executable jar runs](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-extract-specific-libraries-when-an-executable-jar-runs)
+ - [85.7. Create a non-executable JAR with exclusions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-a-nonexecutable-jar)
+ - [85.8. Remote debug a Spring Boot application started with Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-remote-debug-maven-run)
+ - [85.9. Build an executable archive from Ant without using spring-boot-antlib](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-build-an-executable-archive-with-ant)
+ - [86. Traditional deployment](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-traditional-deployment)
+ - [86.1. Create a deployable war file](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-a-deployable-war-file)
+ - [86.2. Create a deployable war file for older servlet containers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-create-a-deployable-war-file-for-older-containers)
+ - [86.3. Convert an existing application to Spring Boot](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-convert-an-existing-application-to-spring-boot)
+ - [86.4. Deploying a WAR to WebLogic](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-weblogic)
+ - [86.5. Deploying a WAR in an Old (Servlet 2.5) Container](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-servlet-2-5)
+ - [86.6. Use Lettuce instead of Jedis](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-use-lettuce-instead-of-jedis)
+
+- [X. Appendices](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#appendix)
+
+ - [A. Common application properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#common-application-properties)
+ - [B. Configuration meta-data](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata)
+ - [B.1. Meta-data format](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-format)
+ - [B.1.1. Group Attributes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-group-attributes)
+ - [B.1.2. Property Attributes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-property-attributes)
+ - [B.1.3. Hint Attributes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-hints-attributes)
+ - [B.1.4. Repeated meta-data items](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-repeated-items)
+ - [B.2. Providing manual hints](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-providing-manual-hints)
+ - [B.2.1. Value hint](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_value_hint)
+ - [B.2.2. Value provider](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_value_provider)
+ - [Any](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_any)
+ - [Class reference](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_class_reference)
+ - [Handle As](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_handle_as)
+ - [Logger name](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_logger_name)
+ - [Spring bean reference](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_spring_bean_reference)
+ - [Spring profile name](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#_spring_profile_name)
+ - [B.3. Generating your own meta-data using the annotation processor](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-annotation-processor)
+ - [B.3.1. Nested properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-nested-properties)
+ - [B.3.2. Adding additional meta-data](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata-additional-metadata)
+ - [C. Auto-configuration classes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#auto-configuration-classes)
+ - [C.1. From the “spring-boot-autoconfigure” module](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#auto-configuration-classes-from-autoconfigure-module)
+ - [C.2. From the “spring-boot-actuator” module](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#auto-configuration-classes-from-actuator)
+ - [D. Test auto-configuration annotations](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#test-auto-configuration)
+ - [E. The executable jar format](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar)
+ - [E.1. Nested JARs](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-nested-jars)
+ - [E.1.1. The executable jar file structure](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-jar-file-structure)
+ - [E.1.2. The executable war file structure](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-war-file-structure)
+ - [E.2. Spring Boot’s “JarFile” class](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-jarfile)
+ - [E.2.1. Compatibility with the standard Java “JarFile”](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-jarfile-compatibility)
+ - [E.3. Launching executable jars](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-launching)
+ - [E.3.1. Launcher manifest](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-launcher-manifest)
+ - [E.3.2. Exploded archives](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-exploded-archives)
+ - [E.4. PropertiesLauncher Features](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-property-launcher-features)
+ - [E.5. Executable jar restrictions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-restrictions)
+ - [E.5.1. Zip entry compression](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-zip-entry-compression)
+ - [E.5.2. System ClassLoader](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-system-classloader)
+ - [E.6. Alternative single jar solutions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar-alternatives)
+ - [F. Dependency versions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#appendix-dependency-versions)
+
+# Part I. Spring Boot Documentation
+
+This section provides a brief overview of Spring Boot reference documentation. Think of it as map for the rest of the document. You can read this reference guide in a linear fashion, or you can skip sections if something doesn’t interest you.
+
+## 1. About the documentation
+
+The Spring Boot reference guide is available as [html](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/html), [pdf](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/pdf/spring-boot-reference.pdf) and [epub](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/epub/spring-boot-reference.epub) documents. The latest copy is available at [docs.spring.io/spring-boot/docs/current/reference](https://docs.spring.io/spring-boot/docs/current/reference).
+
+Copies 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.
+
+## 2. Getting help
+
+Having trouble with Spring Boot, We’d like to help!
+
+- Try the [How-to’s](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto) — they provide solutions to the most common questions.
+- Learn the Spring basics — Spring Boot builds on many other Spring projects, check the [spring.io](https://spring.io/) web-site for a wealth of reference documentation. If you are just starting out with Spring, try one of the [guides](https://spring.io/guides).
+- Ask a question - we monitor [stackoverflow.com](https://stackoverflow.com/) for questions tagged with [`spring-boot`](https://stackoverflow.com/tags/spring-boot).
+- Report bugs with Spring Boot at [github.com/spring-projects/spring-boot/issues](https://github.com/spring-projects/spring-boot/issues).
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| All of Spring Boot is open source, including the documentation! If you find problems with the docs; or if you just want to improve them, please [get involved](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3). |
+
+## 3. First steps
+
+If you’re just getting started with Spring Boot, or 'Spring' in general, [this is the place to start!](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started)
+
+- **From scratch:** [Overview](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-introducing-spring-boot) | [Requirements](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-system-requirements) | [Installation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-installing-spring-boot)
+- **Tutorial:** [Part 1](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application) | [Part 2](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-code)
+- **Running your example:** [Part 1](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-run) | [Part 2](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-executable-jar)
+
+## 4. Working with Spring Boot
+
+Ready to actually start using Spring Boot? [We’ve got you covered](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot).
+
+- **Build systems:** [Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven) | [Gradle](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-gradle) | [Ant](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-ant) | [Starters](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-starter)
+- **Best practices:** [Code Structure](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-structuring-your-code) | [@Configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-configuration-classes) | [@EnableAutoConfiguration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-auto-configuration) | [Beans and Dependency Injection](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-spring-beans-and-dependency-injection)
+- **Running your code** [IDE](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-from-an-ide) | [Packaged](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-as-a-packaged-application) | [Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-with-the-maven-plugin) | [Gradle](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-running-with-the-gradle-plugin)
+- **Packaging your app:** [Production jars](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-packaging-for-production)
+- **Spring Boot CLI:** [Using the CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cli)
+
+## 5. Learning about Spring Boot features
+
+Need more details about Spring Boot’s core features? [This is for you](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features)!
+
+- **Core Features:** [SpringApplication](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-application) | [External Configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config) | [Profiles](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-profiles) | [Logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-logging)
+- **Web Applications:** [MVC](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc) | [Embedded Containers](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-embedded-container)
+- **Working with data:** [SQL](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-sql) | [NO-SQL](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-nosql)
+- **Messaging:** [Overview](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-messaging) | [JMS](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jms)
+- **Testing:** [Overview](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing) | [Boot Applications](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-testing-spring-boot-applications) | [Utils](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-test-utilities)
+- **Extending:** [Auto-configuration](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-developing-auto-configuration) | [@Conditions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-condition-annotations)
+
+## 6. Moving to production
+
+When you’re ready to push your Spring Boot application to production, we’ve got [some tricks that you might like](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready)!
+
+- **Management endpoints:** [Overview](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-endpoints) | [Customization](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-customizing-endpoints)
+- **Connection options:** [HTTP](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-monitoring) | [JMX](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-jmx) |
+- **Monitoring:** [Metrics](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-metrics) | [Auditing](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-auditing) | [Tracing](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-tracing) | [Process](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready-process-monitoring)
+
+## 7. Advanced topics
+
+Lastly, we have a few topics for the more advanced user.
+
+- **Deploy Spring Boot Applications:** [Cloud Deployment](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#cloud-deployment) | [OS Service](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#deployment-service)
+- **Build tool plugins:** [Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-maven-plugin) | [Gradle](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-gradle-plugin)
+- **Appendix:** [Application Properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#common-application-properties) | [Auto-configuration classes](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#auto-configuration-classes) | [Executable Jars](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar)
+
+# Part II. Getting started
+
+
+
+If you’re just getting started with Spring Boot, or 'Spring' in general, this is the section for you! Here we answer the basic “what?”, “how?” and “why?” questions. You’ll find a gentle introduction to Spring Boot along with installation instructions. We’ll then build our first Spring Boot application, discussing some core principles as we go.
+
+## 8. Introducing Spring Boot
+
+Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can “just run”. We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.
+
+You can use Spring Boot to create Java applications that can be started using `java -jar` or more traditional war deployments. We also provide a command line tool that runs “spring scripts”.
+
+Our primary goals are:
+
+- Provide a radically faster and widely accessible getting started experience for all Spring development.
+- Be opinionated out of the box, but get out of the way quickly as requirements start to diverge from the defaults.
+- Provide a range of non-functional features that are common to large classes of projects (e.g. embedded servers, security, metrics, health checks, externalized configuration).
+- Absolutely no code generation and no requirement for XML configuration.
+
+## 9. System Requirements
+
+Spring Boot 2.0.0.M3 requires [Java 8](https://www.java.com/) and Spring Framework 5.0.0.RC3 or above. Explicit build support is provided for Maven (3.2+), and Gradle 3 (3.4 or later).
+
+## 9.1 Servlet containers
+
+The following embedded servlet containers are supported out of the box:
+
+| Name | Servlet Version |
+| ------------ | --------------- |
+| Tomcat 8.5 | 3.1 |
+| Jetty 9.4 | 3.1 |
+| Undertow 1.3 | 3.1 |
+
+You can also deploy Spring Boot applications to any Servlet 3.0+ compatible container.
+
+## 10. Installing Spring Boot
+
+Spring Boot can be used with “classic” Java development tools or installed as a command line tool. Regardless, you will need [Java SDK v1.8](https://www.java.com/) or higher. You should check your current Java installation before you begin:
+
+```
+$ java -version
+```
+
+If you are new to Java development, or if you just want to experiment with Spring Boot you might want to try the [Spring Boot CLI](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-installing-the-cli) first, otherwise, read on for “classic” installation instructions.
+
+## 10.1 Installation instructions for the Java developer
+
+You can use Spring Boot in the same way as any standard Java library. Simply include the appropriate `spring-boot-*.jar` files on your classpath. Spring Boot does not require any special tools integration, so you can use any IDE or text editor; and there is nothing special about a Spring Boot application, so you can run and debug as you would any other Java program.
+
+Although you *could* just copy Spring Boot jars, we generally recommend that you use a build tool that supports dependency management (such as Maven or Gradle).
+
+### 10.1.1 Maven installation
+
+Spring Boot is compatible with Apache Maven 3.2 or above. If you don’t already have Maven installed you can follow the instructions at [maven.apache.org](https://maven.apache.org/).
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| On many operating systems Maven can be installed via a package manager. If you’re an OSX Homebrew user try `brew install maven`. Ubuntu users can run `sudo apt-get install maven`. Windows users with Chocolatey can run `choco install maven` from an elevated prompt. |
+
+Spring Boot dependencies use the `org.springframework.boot` `groupId`. Typically your Maven POM file will inherit from the `spring-boot-starter-parent`project and declare dependencies to one or more [“Starters”](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-starter). Spring Boot also provides an optional [Maven plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-maven-plugin) to create executable jars.
+
+Here is a typical `pom.xml` file:
+
+```
+
+
+ 4.0.0
+
+ com.example
+ myproject
+ 0.0.1-SNAPSHOT
+
+
+
+ org.springframework.boot
+ spring-boot-starter-parent
+ 2.0.0.M3
+
+
+
+
+
+ org.springframework.boot
+ spring-boot-starter-web
+
+
+
+
+
+
+
+ org.springframework.boot
+ spring-boot-maven-plugin
+
+
+
+
+
+
+
+
+ spring-snapshots
+ http://repo.spring.io/snapshot
+ true
+
+
+ spring-milestones
+ http://repo.spring.io/milestone
+
+
+
+
+ spring-snapshots
+ http://repo.spring.io/snapshot
+
+
+ spring-milestones
+ http://repo.spring.io/milestone
+
+
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The `spring-boot-starter-parent` is a great way to use Spring Boot, but it might not be suitable all of the time. Sometimes you may need to inherit from a different parent POM, or you might just not like our default settings. See [Section 13.2.2, “Using Spring Boot without the parent POM”](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven-without-a-parent) for an alternative solution that uses an `import` scope. |
+
+### 10.1.2 Gradle installation
+
+Spring Boot is compatible with Gradle 3 (3.4 or later). If you don’t already have Gradle installed you can follow the instructions at [www.gradle.org/](http://www.gradle.org/).
+
+Spring Boot dependencies can be declared using the `org.springframework.boot` `group`. Typically your project will declare dependencies to one or more[“Starters”](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-starter). Spring Boot provides a useful [Gradle plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-gradle-plugin) that can be used to simplify dependency declarations and to create executable jars.
+
+**Gradle Wrapper**
+
+The Gradle Wrapper provides a nice way of “obtaining” Gradle when you need to build a project. It’s a small script and library that you commit alongside your code to bootstrap the build process. See [docs.gradle.org/3.4.1/userguide/gradle_wrapper.html](https://docs.gradle.org/3.4.1/userguide/gradle_wrapper.html) for details.
+
+Here is a typical `build.gradle` file:
+
+```
+buildscript {
+ repositories {
+ jcenter()
+ maven { url 'http://repo.spring.io/snapshot' }
+ maven { url 'http://repo.spring.io/milestone' }
+ }
+ dependencies {
+ classpath 'org.springframework.boot:spring-boot-gradle-plugin:2.0.0.M3'
+ }
+}
+
+apply plugin: 'java'
+apply plugin: 'org.springframework.boot'
+apply plugin: 'io.spring.dependency-management'
+
+jar {
+ baseName = 'myproject'
+ version = '0.0.1-SNAPSHOT'
+}
+
+repositories {
+ jcenter()
+ maven { url "http://repo.spring.io/snapshot" }
+ maven { url "http://repo.spring.io/milestone" }
+}
+
+dependencies {
+ compile("org.springframework.boot:spring-boot-starter-web")
+ testCompile("org.springframework.boot:spring-boot-starter-test")
+}
+```
+
+## 10.2 Installing the Spring Boot CLI
+
+The Spring Boot CLI is a command line tool that can be used if you want to quickly prototype with Spring. It allows you to run [Groovy](http://groovy.codehaus.org/) scripts, which means that you have a familiar Java-like syntax, without so much boilerplate code.
+
+You don’t need to use the CLI to work with Spring Boot but it’s definitely the quickest way to get a Spring application off the ground.
+
+### 10.2.1 Manual installation
+
+You can download the Spring CLI distribution from the Spring software repository:
+
+- [spring-boot-cli-2.0.0.M3-bin.zip](https://repo.spring.io/milestone/org/springframework/boot/spring-boot-cli/2.0.0.M3/spring-boot-cli-2.0.0.M3-bin.zip)
+- [spring-boot-cli-2.0.0.M3-bin.tar.gz](https://repo.spring.io/milestone/org/springframework/boot/spring-boot-cli/2.0.0.M3/spring-boot-cli-2.0.0.M3-bin.tar.gz)
+
+Cutting edge [snapshot distributions](https://repo.spring.io/snapshot/org/springframework/boot/spring-boot-cli/) are also available.
+
+Once downloaded, follow the [INSTALL.txt](https://raw.github.com/spring-projects/spring-boot/v2.0.0.M3/spring-boot-cli/src/main/content/INSTALL.txt) instructions from the unpacked archive. In summary: there is a `spring` script (`spring.bat` for Windows) in a `bin/`directory in the `.zip` file, or alternatively you can use `java -jar` with the `.jar` file (the script helps you to be sure that the classpath is set correctly).
+
+### 10.2.2 Installation with SDKMAN!
+
+SDKMAN! (The Software Development Kit Manager) can be used for managing multiple versions of various binary SDKs, including Groovy and the Spring Boot CLI. Get SDKMAN! from [sdkman.io](http://sdkman.io/) and install Spring Boot with
+
+```
+$ sdk install springboot
+$ spring --version
+Spring Boot v2.0.0.M3
+```
+
+If you are developing features for the CLI and want easy access to the version you just built, follow these extra instructions.
+
+```
+$ sdk install springboot dev /path/to/spring-boot/spring-boot-cli/target/spring-boot-cli-2.0.0.M3-bin/spring-2.0.0.M3/
+$ sdk default springboot dev
+$ spring --version
+Spring CLI v2.0.0.M3
+```
+
+This will install a local instance of `spring` called the `dev` instance. It points at your target build location, so every time you rebuild Spring Boot, `spring` will be up-to-date.
+
+You can see it by doing this:
+
+```
+$ sdk ls springboot
+
+================================================================================
+Available Springboot Versions
+================================================================================
+> + dev
+* 2.0.0.M3
+
+================================================================================
++ - local version
+* - installed
+> - currently in use
+================================================================================
+```
+
+### 10.2.3 OSX Homebrew installation
+
+If you are on a Mac and using [Homebrew](https://brew.sh/), all you need to do to install the Spring Boot CLI is:
+
+```
+$ brew tap pivotal/tap
+$ brew install springboot
+```
+
+Homebrew will install `spring` to `/usr/local/bin`.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you don’t see the formula, your installation of brew might be out-of-date. Just execute `brew update` and try again. |
+
+### 10.2.4 MacPorts installation
+
+If you are on a Mac and using [MacPorts](https://www.macports.org/), all you need to do to install the Spring Boot CLI is:
+
+```
+$ sudo port install spring-boot-cli
+```
+
+### 10.2.5 Command-line completion
+
+Spring Boot CLI ships with scripts that provide command completion for [BASH](https://en.wikipedia.org/wiki/Bash_(Unix_shell)) and [zsh](https://en.wikipedia.org/wiki/Zsh) shells. You can `source` the script (also named `spring`) in any shell, or put it in your personal or system-wide bash completion initialization. On a Debian system the system-wide scripts are in `/shell-completion/bash` and all scripts in that directory are executed when a new shell starts. To run the script manually, e.g. if you have installed using SDKMAN!
+
+```
+$ . ~/.sdkman/candidates/springboot/current/shell-completion/bash/spring
+$ spring
+ grab help jar run test version
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you install Spring Boot CLI using Homebrew or MacPorts, the command-line completion scripts are automatically registered with your shell. |
+
+### 10.2.6 Quick start Spring CLI example
+
+Here’s a really simple web application that you can use to test your installation. Create a file called `app.groovy`:
+
+```
+@RestController
+class ThisWillActuallyRun {
+
+ @RequestMapping("/")
+ String home() {
+ "Hello World!"
+ }
+
+}
+
+```
+
+Then simply run it from a shell:
+
+```
+$ spring run app.groovy
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| It will take some time when you first run the application as dependencies are downloaded. Subsequent runs will be much quicker. |
+
+Open [localhost:8080](http://localhost:8080/) in your favorite web browser and you should see the following output:
+
+```
+Hello World!
+
+```
+
+## 10.3 Upgrading from an earlier version of Spring Boot
+
+If you are upgrading from an earlier release of Spring Boot check the “release notes” hosted on the [project wiki](https://github.com/spring-projects/spring-boot/wiki). You’ll find upgrade instructions along with a list of “new and noteworthy” features for each release.
+
+To upgrade an existing CLI installation use the appropriate package manager command (for example `brew upgrade`) or, if you manually installed the CLI, follow the[standard instructions](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-manual-cli-installation) remembering to update your `PATH` environment variable to remove any older references.
+
+## 11. Developing your first Spring Boot application
+
+Let’s develop a simple “Hello World!” web application in Java that highlights some of Spring Boot’s key features. We’ll use Maven to build this project since most IDEs support it.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The [spring.io](https://spring.io/) web site contains many “Getting Started” guides that use Spring Boot. If you’re looking to solve a specific problem; check there first.You can shortcut the steps below by going to [start.spring.io](https://start.spring.io/) and choosing the `web` starter from the dependencies searcher. This will automatically generate a new project structure so that you can [start coding right away](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#getting-started-first-application-code). Check the [documentation for more details](https://github.com/spring-io/initializr). |
+
+Before we begin, open a terminal to check that you have valid versions of Java and Maven installed.
+
+```
+$ java -version
+java version "1.8.0_102"
+Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
+Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
+$ mvn -v
+Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00)
+Maven home: /usr/local/Cellar/maven/3.3.9/libexec
+Java version: 1.8.0_102, vendor: Oracle Corporation
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| This sample needs to be created in its own folder. Subsequent instructions assume that you have created a suitable folder and that it is your “current directory”. |
+
+## 11.1 Creating the POM
+
+We need to start by creating a Maven `pom.xml` file. The `pom.xml` is the recipe that will be used to build your project. Open your favorite text editor and add the following:
+
+```
+
+
+ 4.0.0
+
+ com.example
+ myproject
+ 0.0.1-SNAPSHOT
+
+
+ org.springframework.boot
+ spring-boot-starter-parent
+ 2.0.0.M3
+
+
+
+
+
+
+
+ spring-snapshots
+ http://repo.spring.io/snapshot
+ true
+
+
+ spring-milestones
+ http://repo.spring.io/milestone
+
+
+
+
+ spring-snapshots
+ http://repo.spring.io/snapshot
+
+
+ spring-milestones
+ http://repo.spring.io/milestone
+
+
+
+
+```
+
+This should give you a working build, you can test it out by running `mvn package` (you can ignore the “jar will be empty - no content was marked for inclusion!” warning for now).
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| At this point you could import the project into an IDE (most modern Java IDE’s include built-in support for Maven). For simplicity, we will continue to use a plain text editor for this example. |
+
+## 11.2 Adding classpath dependencies
+
+Spring Boot provides a number of “Starters” that make easy to add jars to your classpath. Our sample application has already used `spring-boot-starter-parent`in the `parent` section of the POM. The `spring-boot-starter-parent` is a special starter that provides useful Maven defaults. It also provides a[`dependency-management`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-dependency-management) section so that you can omit `version` tags for “blessed” dependencies.
+
+Other “Starters” simply provide dependencies that you are likely to need when developing a specific type of application. Since we are developing a web application, we will add a `spring-boot-starter-web` dependency — but before that, let’s look at what we currently have.
+
+```
+$ mvn dependency:tree
+
+[INFO] com.example:myproject:jar:0.0.1-SNAPSHOT
+
+```
+
+The `mvn dependency:tree` command prints a tree representation of your project dependencies. You can see that `spring-boot-starter-parent` provides no dependencies by itself. Let’s edit our `pom.xml` and add the `spring-boot-starter-web` dependency just below the `parent` section:
+
+```
+
+
+ org.springframework.boot
+ spring-boot-starter-web
+
+
+
+```
+
+If you run `mvn dependency:tree` again, you will see that there are now a number of additional dependencies, including the Tomcat web server and Spring Boot itself.
+
+## 11.3 Writing the code
+
+To finish our application we need to create a single Java file. Maven will compile sources from `src/main/java` by default so you need to create that folder structure, then add a file named `src/main/java/Example.java`:
+
+```
+import org.springframework.boot.*;
+import org.springframework.boot.autoconfigure.*;
+import org.springframework.stereotype.*;
+import org.springframework.web.bind.annotation.*;
+
+@RestController
+@EnableAutoConfiguration
+public class Example {
+
+ @RequestMapping("/")
+ String home() {
+ return "Hello World!";
+ }
+
+ public static void main(String[] args) throws Exception {
+ SpringApplication.run(Example.class, args);
+ }
+
+}
+
+```
+
+Although there isn’t much code here, quite a lot is going on. Let’s step through the important parts.
+
+### 11.3.1 The @RestController and @RequestMapping annotations
+
+The first annotation on our `Example` class is `@RestController`. This is known as a *stereotype* annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web `@Controller` so Spring will consider it when handling incoming web requests.
+
+The `@RequestMapping` annotation provides “routing” information. It is telling Spring that any HTTP request with the path “/” should be mapped to the `home` method. The `@RestController` annotation tells Spring to render the resulting string directly back to the caller.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The `@RestController` and `@RequestMapping` annotations are Spring MVC annotations (they are not specific to Spring Boot). See the [MVC section](https://docs.spring.io/spring/docs/5.0.0.RC3/spring-framework-reference/web.html#mvc)in the Spring Reference Documentation for more details. |
+
+### 11.3.2 The @EnableAutoConfiguration annotation
+
+The second class-level annotation is `@EnableAutoConfiguration`. This annotation tells Spring Boot to “guess” how you will want to configure Spring, based on the jar dependencies that you have added. Since `spring-boot-starter-web` added Tomcat and Spring MVC, the auto-configuration will assume that you are developing a web application and setup Spring accordingly.
+
+**Starters and Auto-Configuration**
+
+Auto-configuration is designed to work well with “Starters”, but the two concepts are not directly tied. You are free to pick-and-choose jar dependencies outside of the starters and Spring Boot will still do its best to auto-configure your application.
+
+### 11.3.3 The “main” method
+
+The final part of our application is the `main` method. This is just a standard method that follows the Java convention for an application entry point. Our main method delegates to Spring Boot’s `SpringApplication` class by calling `run`. `SpringApplication` will bootstrap our application, starting Spring which will in turn start the auto-configured Tomcat web server. We need to pass `Example.class` as an argument to the `run` method to tell `SpringApplication` which is the primary Spring component. The `args` array is also passed through to expose any command-line arguments.
+
+## 11.4 Running the example
+
+At this point our application should work. Since we have used the `spring-boot-starter-parent` POM we have a useful `run` goal that we can use to start the application. Type `mvn spring-boot:run` from the root project directory to start the application:
+
+```
+$ mvn spring-boot:run
+
+ . ____ _ __ _ _
+ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
+( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
+ \\/ ___)| |_)| | | | | || (_| | ) ) ) )
+ ' |____| .__|_| |_|_| |_\__, | / / / /
+ =========|_|==============|___/=/_/_/_/
+ :: Spring Boot :: (v2.0.0.M3)
+....... . . .
+....... . . . (log output here)
+....... . . .
+........ Started Example in 2.222 seconds (JVM running for 6.514)
+
+```
+
+If you open a web browser to [localhost:8080](http://localhost:8080/) you should see the following output:
+
+```
+Hello World!
+
+```
+
+To gracefully exit the application hit `ctrl-c`.
+
+## 11.5 Creating an executable jar
+
+Let’s finish our example by creating a completely self-contained executable jar file that we could run in production. Executable jars (sometimes called “fat jars”) are archives containing your compiled classes along with all of the jar dependencies that your code needs to run.
+
+**Executable jars and Java**
+
+Java does not provide any standard way to load nested jar files (i.e. jar files that are themselves contained within a jar). This can be problematic if you are looking to distribute a self-contained application.
+
+To solve this problem, many developers use “uber” jars. An uber jar simply packages all classes, from all jars, into a single archive. The problem with this approach is that it becomes hard to see which libraries you are actually using in your application. It can also be problematic if the same filename is used (but with different content) in multiple jars.
+
+Spring Boot takes a [different approach](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#executable-jar) and allows you to actually nest jars directly.
+
+To create an executable jar we need to add the `spring-boot-maven-plugin` to our `pom.xml`. Insert the following lines just below the `dependencies` section:
+
+```
+
+
+
+ org.springframework.boot
+ spring-boot-maven-plugin
+
+
+
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| The `spring-boot-starter-parent` POM includes `` configuration to bind the `repackage` goal. If you are not using the parent POM you will need to declare this configuration yourself. See the [plugin documentation](https://docs.spring.io/spring-boot/docs/2.0.0.M3/maven-plugin//usage.html) for details. |
+
+Save your `pom.xml` and run `mvn package` from the command line:
+
+```
+$ mvn package
+
+[INFO] Scanning for projects...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Building myproject 0.0.1-SNAPSHOT
+[INFO] ------------------------------------------------------------------------
+[INFO] .... ..
+[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ myproject ---
+[INFO] Building jar: /Users/developer/example/spring-boot-example/target/myproject-0.0.1-SNAPSHOT.jar
+[INFO]
+[INFO] --- spring-boot-maven-plugin:2.0.0.M3:repackage (default) @ myproject ---
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+
+```
+
+If you look in the `target` directory you should see `myproject-0.0.1-SNAPSHOT.jar`. The file should be around 10 MB in size. If you want to peek inside, you can use `jar tvf`:
+
+```
+$ jar tvf target/myproject-0.0.1-SNAPSHOT.jar
+
+```
+
+You should also see a much smaller file named `myproject-0.0.1-SNAPSHOT.jar.original` in the `target` directory. This is the original jar file that Maven created before it was repackaged by Spring Boot.
+
+To run that application, use the `java -jar` command:
+
+```
+$ java -jar target/myproject-0.0.1-SNAPSHOT.jar
+
+ . ____ _ __ _ _
+ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
+( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
+ \\/ ___)| |_)| | | | | || (_| | ) ) ) )
+ ' |____| .__|_| |_|_| |_\__, | / / / /
+ =========|_|==============|___/=/_/_/_/
+ :: Spring Boot :: (v2.0.0.M3)
+....... . . .
+....... . . . (log output here)
+....... . . .
+........ Started Example in 2.536 seconds (JVM running for 2.864)
+
+```
+
+As before, to gracefully exit the application hit `ctrl-c`.
+
+## 12. What to read next
+
+Hopefully this section has provided you with some of the Spring Boot basics, and got you on your way to writing your own applications. If you’re a task-oriented type of developer you might want to jump over to [spring.io](https://spring.io/) and check out some of the [getting started](https://spring.io/guides/) guides that solve specific “How do I do that with Spring” problems; we also have Spring Boot-specific *How-to* reference documentation.
+
+The [Spring Boot repository](https://github.com/spring-projects/spring-boot) has also a [bunch of samples](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-samples) you can run. The samples are independent of the rest of the code (that is you don’t need to build the rest to run or use the samples).
+
+Otherwise, the next logical step is to read *Part III, “Using Spring Boot”*. If you’re really impatient, you could also jump ahead and read about *Spring Boot features*.
+
+# Part III. Using Spring Boot
+
+
+
+This section goes into more detail about how you should use Spring Boot. It covers topics such as build systems, auto-configuration and how to run your applications. We also cover some Spring Boot best practices. Although there is nothing particularly special about Spring Boot (it is just another library that you can consume), there are a few recommendations that, when followed, will make your development process just a little easier.
+
+If you’re just starting out with Spring Boot, you should probably read the *Getting Started* guide before diving into this section.
+
+## 13. Build systems
+
+It is strongly recommended that you choose a build system that supports [*dependency management*](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-dependency-management), and one that can consume artifacts published to the “Maven Central” repository. We would recommend that you choose Maven or Gradle. It is possible to get Spring Boot to work with other build systems (Ant for example), but they will not be particularly well supported.
+
+## 13.1 Dependency management
+
+Each release of Spring Boot provides a curated list of dependencies it supports. In practice, you do not need to provide a version for any of these dependencies in your build configuration as Spring Boot is managing that for you. When you upgrade Spring Boot itself, these dependencies will be upgraded as well in a consistent way.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| You can still specify a version and override Spring Boot’s recommendations if you feel that’s necessary. |
+
+The curated list contains all the spring modules that you can use with Spring Boot as well as a refined list of third party libraries. The list is available as a standard [Bills of Materials (`spring-boot-dependencies`)](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven-without-a-parent) that can be used with both [Maven](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-maven-parent-pom) and [Gradle](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-gradle).
+
+| ![[Warning]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/warning.png) |
+| ------------------------------------------------------------ |
+| Each release of Spring Boot is associated with a base version of the Spring Framework so we **highly** recommend you to not specify its version on your own. |
+
+## 13.2 Maven
+
+Maven users can inherit from the `spring-boot-starter-parent` project to obtain sensible defaults. The parent project provides the following features:
+
+- Java 1.8 as the default compiler level.
+- UTF-8 source encoding.
+- A [Dependency Management section](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-dependency-management), allowing you to omit `` tags for common dependencies, inherited from the `spring-boot-dependencies` POM.
+- Sensible [resource filtering](https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html).
+- Sensible plugin configuration ([exec plugin](http://www.mojohaus.org/exec-maven-plugin/), [surefire](https://maven.apache.org/surefire/maven-surefire-plugin/), [Git commit ID](https://github.com/ktoso/maven-git-commit-id-plugin), [shade](https://maven.apache.org/plugins/maven-shade-plugin/)).
+- Sensible resource filtering for `application.properties` and `application.yml` including profile-specific files (e.g. `application-foo.properties` and `application-foo.yml`)
+
+On the last point: since the default config files accept Spring style placeholders (`${…}`) the Maven filtering is changed to use `@..@` placeholders (you can override that with a Maven property `resource.delimiter`).
+
+### 13.2.1 Inheriting the starter parent
+
+To configure your project to inherit from the `spring-boot-starter-parent` simply set the `parent`:
+
+```
+
+
+ org.springframework.boot
+ spring-boot-starter-parent
+ 2.0.0.M3
+
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| You should only need to specify the Spring Boot version number on this dependency. If you import additional starters, you can safely omit the version number. |
+
+With that setup, you can also override individual dependencies by overriding a property in your own project. For instance, to upgrade to another Spring Data release train you’d add the following to your `pom.xml`.
+
+```
+
+ Fowler-SR2
+
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Check the [`spring-boot-dependencies` pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-dependencies/pom.xml) for a list of supported properties. |
+
+### 13.2.2 Using Spring Boot without the parent POM
+
+Not everyone likes inheriting from the `spring-boot-starter-parent` POM. You may have your own corporate standard parent that you need to use, or you may just prefer to explicitly declare all your Maven configuration.
+
+If you don’t want to use the `spring-boot-starter-parent`, you can still keep the benefit of the dependency management (but not the plugin management) by using a `scope=import` dependency:
+
+```
+
+
+
+
+ org.springframework.boot
+ spring-boot-dependencies
+ 2.0.0.M3
+ pom
+ import
+
+
+
+
+```
+
+That setup does not allow you to override individual dependencies using a property as explained above. To achieve the same result, you’d need to add an entry in the`dependencyManagement` of your project **before** the `spring-boot-dependencies` entry. For instance, to upgrade to another Spring Data release train you’d add the following to your `pom.xml`.
+
+```
+
+
+
+
+ org.springframework.data
+ spring-data-releasetrain
+ Fowler-SR2
+ import
+ pom
+
+
+ org.springframework.boot
+ spring-boot-dependencies
+ 2.0.0.M3
+ pom
+ import
+
+
+
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| In the example above, we specify a *BOM* but any dependency type can be overridden that way. |
+
+### 13.2.3 Using the Spring Boot Maven plugin
+
+Spring Boot includes a [Maven plugin](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#build-tool-plugins-maven-plugin) that can package the project as an executable jar. Add the plugin to your `` section if you want to use it:
+
+```
+
+
+
+ org.springframework.boot
+ spring-boot-maven-plugin
+
+
+
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you use the Spring Boot starter parent pom, you only need to add the plugin, there is no need for to configure it unless you want to change the settings defined in the parent. |
+
+## 13.3 Gradle
+
+To learn about using Spring Boot with Gradle, please refer to the documentation for Spring Boot’s Gradle plugin:
+
+- Reference ([HTML](https://docs.spring.io/spring-boot/docs/2.0.0.M3/gradle-plugin//reference/html) and [PDF](https://docs.spring.io/spring-boot/docs/2.0.0.M3/gradle-plugin//reference/pdf/spring-boot-gradle-plugin-reference.pdf))
+- [API](https://docs.spring.io/spring-boot/docs/2.0.0.M3/gradle-plugin//api)
+
+## 13.4 Ant
+
+It is possible to build a Spring Boot project using Apache Ant+Ivy. The `spring-boot-antlib` “AntLib” module is also available to help Ant create executable jars.
+
+To declare dependencies a typical `ivy.xml` file will look something like this:
+
+```
+
+
+
+
+
+
+
+
+
+
+
+```
+
+A typical `build.xml` will look like this:
+
+```
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| See the *Section 85.9, “Build an executable archive from Ant without using spring-boot-antlib”* “How-to” if you don’t want to use the `spring-boot-antlib`module. |
+
+## 13.5 Starters
+
+Starters are a set of convenient dependency descriptors that you can include in your application. You get a one-stop-shop for all the Spring and related technology that you need, without having to hunt through sample code and copy paste loads of dependency descriptors. For example, if you want to get started using Spring and JPA for database access, just include the `spring-boot-starter-data-jpa` dependency in your project, and you are good to go.
+
+The starters contain a lot of the dependencies that you need to get a project up and running quickly and with a consistent, supported set of managed transitive dependencies.
+
+**What’s in a name**
+
+All **official** starters follow a similar naming pattern; `spring-boot-starter-*`, where `*` is a particular type of application. This naming structure is intended to help when you need to find a starter. The Maven integration in many IDEs allow you to search dependencies by name. For example, with the appropriate Eclipse or STS plugin installed, you can simply hit `ctrl-space` in the POM editor and type “spring-boot-starter” for a complete list.
+
+As explained in the [Creating your own starter](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-starter) section, third party starters should not start with `spring-boot` as it is reserved for official Spring Boot artifacts. A third-party starter for `acme` will be typically named `acme-spring-boot-starter`.
+
+The following application starters are provided by Spring Boot under the `org.springframework.boot` group:
+
+
+
+**Table 13.1. Spring Boot application starters**
+
+| Name | Description | Pom |
+| --------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| `spring-boot-starter` | Core starter, including auto-configuration support, logging and YAML | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter/pom.xml) |
+| `spring-boot-starter-activemq` | Starter for JMS messaging using Apache ActiveMQ | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-activemq/pom.xml) |
+| `spring-boot-starter-amqp` | Starter for using Spring AMQP and Rabbit MQ | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-amqp/pom.xml) |
+| `spring-boot-starter-aop` | Starter for aspect-oriented programming with Spring AOP and AspectJ | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-aop/pom.xml) |
+| `spring-boot-starter-artemis` | Starter for JMS messaging using Apache Artemis | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-artemis/pom.xml) |
+| `spring-boot-starter-batch` | Starter for using Spring Batch | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-batch/pom.xml) |
+| `spring-boot-starter-cache` | Starter for using Spring Framework’s caching support | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-cache/pom.xml) |
+| `spring-boot-starter-cloud-connectors` | Starter for using Spring Cloud Connectors which simplifies connecting to services in cloud platforms like Cloud Foundry and Heroku | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-cloud-connectors/pom.xml) |
+| `spring-boot-starter-data-cassandra` | Starter for using Cassandra distributed database and Spring Data Cassandra | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-cassandra/pom.xml) |
+| `spring-boot-starter-data-cassandra-reactive` | Starter for using Cassandra distributed database and Spring Data Cassandra Reactive | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-cassandra-reactive/pom.xml) |
+| `spring-boot-starter-data-couchbase` | Starter for using Couchbase document-oriented database and Spring Data Couchbase | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-couchbase/pom.xml) |
+| `spring-boot-starter-data-elasticsearch` | Starter for using Elasticsearch search and analytics engine and Spring Data Elasticsearch | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-elasticsearch/pom.xml) |
+| `spring-boot-starter-data-jpa` | Starter for using Spring Data JPA with Hibernate | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-jpa/pom.xml) |
+| `spring-boot-starter-data-ldap` | Starter for using Spring Data LDAP | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-ldap/pom.xml) |
+| `spring-boot-starter-data-mongodb` | Starter for using MongoDB document-oriented database and Spring Data MongoDB | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-mongodb/pom.xml) |
+| `spring-boot-starter-data-mongodb-reactive` | Starter for using MongoDB document-oriented database and Spring Data MongoDB Reactive | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-mongodb-reactive/pom.xml) |
+| `spring-boot-starter-data-neo4j` | Starter for using Neo4j graph database and Spring Data Neo4j | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-neo4j/pom.xml) |
+| `spring-boot-starter-data-redis` | Starter for using Redis key-value data store with Spring Data Redis and the Jedis client | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-redis/pom.xml) |
+| `spring-boot-starter-data-redis-reactive` | Starter for using Redis key-value data store with Spring Data Redis reactive and the Lettuce client | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-redis-reactive/pom.xml) |
+| `spring-boot-starter-data-rest` | Starter for exposing Spring Data repositories over REST using Spring Data REST | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-rest/pom.xml) |
+| `spring-boot-starter-data-solr` | Starter for using the Apache Solr search platform with Spring Data Solr | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-data-solr/pom.xml) |
+| `spring-boot-starter-freemarker` | Starter for building MVC web applications using FreeMarker views | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-freemarker/pom.xml) |
+| `spring-boot-starter-groovy-templates` | Starter for building MVC web applications using Groovy Templates views | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-groovy-templates/pom.xml) |
+| `spring-boot-starter-hateoas` | Starter for building hypermedia-based RESTful web application with Spring MVC and Spring HATEOAS | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-hateoas/pom.xml) |
+| `spring-boot-starter-integration` | Starter for using Spring Integration | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-integration/pom.xml) |
+| `spring-boot-starter-jdbc` | Starter for using JDBC with the Tomcat JDBC connection pool | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jdbc/pom.xml) |
+| `spring-boot-starter-jersey` | Starter for building RESTful web applications using JAX-RS and Jersey. An alternative to [`spring-boot-starter-web`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-web) | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jersey/pom.xml) |
+| `spring-boot-starter-jooq` | Starter for using jOOQ to access SQL databases. An alternative to [`spring-boot-starter-data-jpa`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-data-jpa) or [`spring-boot-starter-jdbc`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-jdbc) | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jooq/pom.xml) |
+| `spring-boot-starter-jta-atomikos` | Starter for JTA transactions using Atomikos | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jta-atomikos/pom.xml) |
+| `spring-boot-starter-jta-bitronix` | Starter for JTA transactions using Bitronix | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jta-bitronix/pom.xml) |
+| `spring-boot-starter-jta-narayana` | Spring Boot Narayana JTA Starter | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jta-narayana/pom.xml) |
+| `spring-boot-starter-mail` | Starter for using Java Mail and Spring Framework’s email sending support | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-mail/pom.xml) |
+| `spring-boot-starter-mobile` | Starter for building web applications using Spring Mobile | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-mobile/pom.xml) |
+| `spring-boot-starter-mustache` | Starter for building web applications using Mustache views | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-mustache/pom.xml) |
+| `spring-boot-starter-quartz` | Spring Boot Quartz Starter | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-quartz/pom.xml) |
+| `spring-boot-starter-security` | Starter for using Spring Security | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-security/pom.xml) |
+| `spring-boot-starter-social-facebook` | Starter for using Spring Social Facebook | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-social-facebook/pom.xml) |
+| `spring-boot-starter-social-linkedin` | Stater for using Spring Social LinkedIn | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-social-linkedin/pom.xml) |
+| `spring-boot-starter-social-twitter` | Starter for using Spring Social Twitter | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-social-twitter/pom.xml) |
+| `spring-boot-starter-test` | Starter for testing Spring Boot applications with libraries including JUnit, Hamcrest and Mockito | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-test/pom.xml) |
+| `spring-boot-starter-thymeleaf` | Starter for building MVC web applications using Thymeleaf views | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-thymeleaf/pom.xml) |
+| `spring-boot-starter-validation` | Starter for using Java Bean Validation with Hibernate Validator | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-validation/pom.xml) |
+| `spring-boot-starter-web` | Starter for building web, including RESTful, applications using Spring MVC. Uses Tomcat as the default embedded container | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-web/pom.xml) |
+| `spring-boot-starter-web-services` | Starter for using Spring Web Services | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-web-services/pom.xml) |
+| `spring-boot-starter-webflux` | Starter for building WebFlux applications using Spring Framework’s Reactive Web support | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-webflux/pom.xml) |
+| `spring-boot-starter-websocket` | Starter for building WebSocket applications using Spring Framework’s WebSocket support | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-websocket/pom.xml) |
+
+In addition to the application starters, the following starters can be used to add *production ready* features:
+
+
+
+**Table 13.2. Spring Boot production starters**
+
+| Name | Description | Pom |
+| ------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| `spring-boot-starter-actuator` | Starter for using Spring Boot’s Actuator which provides production ready features to help you monitor and manage your application | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-actuator/pom.xml) |
+
+Finally, Spring Boot also includes some starters that can be used if you want to exclude or swap specific technical facets:
+
+
+
+**Table 13.3. Spring Boot technical starters**
+
+| Name | Description | Pom |
+| ----------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| `spring-boot-starter-jetty` | Starter for using Jetty as the embedded servlet container. An alternative to [`spring-boot-starter-tomcat`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-tomcat) | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-jetty/pom.xml) |
+| `spring-boot-starter-json` | Starter for reading and writing json | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-json/pom.xml) |
+| `spring-boot-starter-log4j2` | Starter for using Log4j2 for logging. An alternative to [`spring-boot-starter-logging`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-logging) | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-log4j2/pom.xml) |
+| `spring-boot-starter-logging` | Starter for logging using Logback. Default logging starter | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-logging/pom.xml) |
+| `spring-boot-starter-reactor-netty` | Starter for using Reactor Netty as the embedded reactive HTTP server. | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-reactor-netty/pom.xml) |
+| `spring-boot-starter-tomcat` | Starter for using Tomcat as the embedded servlet container. Default servlet container starter used by [`spring-boot-starter-web`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-web) | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-tomcat/pom.xml) |
+| `spring-boot-starter-undertow` | Starter for using Undertow as the embedded servlet container. An alternative to [`spring-boot-starter-tomcat`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#spring-boot-starter-tomcat) | [Pom](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-starters/spring-boot-starter-undertow/pom.xml) |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| For a list of additional community contributed starters, see the [README file](https://github.com/spring-projects/spring-boot/tree/master/spring-boot-starters/README.adoc) in the `spring-boot-starters` module on GitHub. |
+
+## 14. Structuring your code
+
+Spring Boot does not require any specific code layout to work, however, there are some best practices that help.
+
+## 14.1 Using the “default” package
+
+When a class doesn’t include a `package` declaration it is considered to be in the “default package”. The use of the “default package” is generally discouraged, and should be avoided. It can cause particular problems for Spring Boot applications that use `@ComponentScan`, `@EntityScan` or `@SpringBootApplication`annotations, since every class from every jar, will be read.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| We recommend that you follow Java’s recommended package naming conventions and use a reversed domain name (for example, `com.example.project`). |
+
+## 14.2 Locating the main application class
+
+We generally recommend that you locate your main application class in a root package above other classes. The `@EnableAutoConfiguration` annotation is often placed on your main class, and it implicitly defines a base “search package” for certain items. For example, if you are writing a JPA application, the package of the`@EnableAutoConfiguration` annotated class will be used to search for `@Entity` items.
+
+Using a root package also allows the `@ComponentScan` annotation to be used without needing to specify a `basePackage` attribute. You can also use the`@SpringBootApplication` annotation if your main class is in the root package.
+
+Here is a typical layout:
+
+```
+com
+ +- example
+ +- myproject
+ +- Application.java
+ |
+ +- domain
+ | +- Customer.java
+ | +- CustomerRepository.java
+ |
+ +- service
+ | +- CustomerService.java
+ |
+ +- web
+ +- CustomerController.java
+
+```
+
+The `Application.java` file would declare the `main` method, along with the basic `@Configuration`.
+
+```
+package com.example.myproject;
+
+import org.springframework.boot.SpringApplication;
+import org.springframework.boot.autoconfigure.EnableAutoConfiguration;
+import org.springframework.context.annotation.ComponentScan;
+import org.springframework.context.annotation.Configuration;
+
+@Configuration
+@EnableAutoConfiguration
+@ComponentScan
+public class Application {
+
+ public static void main(String[] args) {
+ SpringApplication.run(Application.class, args);
+ }
+
+}
+
+```
+
+## 15. Configuration classes
+
+Spring Boot favors Java-based configuration. Although it is possible to use `SpringApplication` with an XML sources, we generally recommend that your primary source is a single `@Configuration` class. Usually the class that defines the `main` method is also a good candidate as the primary `@Configuration`.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Many Spring configuration examples have been published on the Internet that use XML configuration. Always try to use the equivalent Java-based configuration if possible. Searching for `Enable*` annotations can be a good starting point. |
+
+## 15.1 Importing additional configuration classes
+
+You don’t need to put all your `@Configuration` into a single class. The `@Import` annotation can be used to import additional configuration classes. Alternatively, you can use `@ComponentScan` to automatically pick up all Spring components, including `@Configuration` classes.
+
+## 15.2 Importing XML configuration
+
+If you absolutely must use XML based configuration, we recommend that you still start with a `@Configuration` class. You can then use an additional `@ImportResource` annotation to load XML configuration files.
+
+## 16. Auto-configuration
+
+Spring Boot auto-configuration attempts to automatically configure your Spring application based on the jar dependencies that you have added. For example, If `HSQLDB`is on your classpath, and you have not manually configured any database connection beans, then we will auto-configure an in-memory database.
+
+You need to opt-in to auto-configuration by adding the `@EnableAutoConfiguration` or `@SpringBootApplication` annotations to one of your `@Configuration` classes.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| You should only ever add one `@EnableAutoConfiguration` annotation. We generally recommend that you add it to your primary `@Configuration`class. |
+
+## 16.1 Gradually replacing auto-configuration
+
+Auto-configuration is noninvasive, at any point you can start to define your own configuration to replace specific parts of the auto-configuration. For example, if you add your own `DataSource` bean, the default embedded database support will back away.
+
+If you need to find out what auto-configuration is currently being applied, and why, start your application with the `--debug` switch. This will enable debug logs for a selection of core loggers and log an auto-configuration report to the console.
+
+## 16.2 Disabling specific auto-configuration
+
+If you find that specific auto-configure classes are being applied that you don’t want, you can use the exclude attribute of `@EnableAutoConfiguration` to disable them.
+
+```
+import org.springframework.boot.autoconfigure.*;
+import org.springframework.boot.autoconfigure.jdbc.*;
+import org.springframework.context.annotation.*;
+
+@Configuration
+@EnableAutoConfiguration(exclude={DataSourceAutoConfiguration.class})
+public class MyConfiguration {
+}
+
+```
+
+If the class is not on the classpath, you can use the `excludeName` attribute of the annotation and specify the fully qualified name instead. Finally, you can also control the list of auto-configuration classes to exclude via the `spring.autoconfigure.exclude` property.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| You can define exclusions both at the annotation level and using the property. |
+
+## 17. Spring Beans and dependency injection
+
+You are free to use any of the standard Spring Framework techniques to define your beans and their injected dependencies. For simplicity, we often find that using `@ComponentScan` to find your beans, in combination with `@Autowired` constructor injection works well.
+
+If you structure your code as suggested above (locating your application class in a root package), you can add `@ComponentScan` without any arguments. All of your application components (`@Component`, `@Service`, `@Repository`, `@Controller` etc.) will be automatically registered as Spring Beans.
+
+Here is an example `@Service` Bean that uses constructor injection to obtain a required `RiskAssessor` bean.
+
+```
+package com.example.service;
+
+import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.stereotype.Service;
+
+@Service
+public class DatabaseAccountService implements AccountService {
+
+ private final RiskAssessor riskAssessor;
+
+ @Autowired
+ public DatabaseAccountService(RiskAssessor riskAssessor) {
+ this.riskAssessor = riskAssessor;
+ }
+
+ // ...
+
+}
+
+```
+
+And if a bean has one constructor, you can omit the `@Autowired`.
+
+```
+@Service
+public class DatabaseAccountService implements AccountService {
+
+ private final RiskAssessor riskAssessor;
+
+ public DatabaseAccountService(RiskAssessor riskAssessor) {
+ this.riskAssessor = riskAssessor;
+ }
+
+ // ...
+
+}
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Notice how using constructor injection allows the `riskAssessor` field to be marked as `final`, indicating that it cannot be subsequently changed. |
+
+## 18. Using the @SpringBootApplication annotation
+
+Many Spring Boot developers always have their main class annotated with `@Configuration`, `@EnableAutoConfiguration` and `@ComponentScan`. Since these annotations are so frequently used together (especially if you follow the [best practices](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-structuring-your-code) above), Spring Boot provides a convenient `@SpringBootApplication`alternative.
+
+The `@SpringBootApplication` annotation is equivalent to using `@Configuration`, `@EnableAutoConfiguration` and `@ComponentScan` with their default attributes:
+
+```
+package com.example.myproject;
+
+import org.springframework.boot.SpringApplication;
+import org.springframework.boot.autoconfigure.SpringBootApplication;
+
+@SpringBootApplication // same as @Configuration @EnableAutoConfiguration @ComponentScan
+public class Application {
+
+ public static void main(String[] args) {
+ SpringApplication.run(Application.class, args);
+ }
+
+}
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| `@SpringBootApplication` also provides aliases to customize the attributes of `@EnableAutoConfiguration` and `@ComponentScan`. |
+
+## 19. Running your application
+
+One of the biggest advantages of packaging your application as jar and using an embedded HTTP server is that you can run your application as you would any other. Debugging Spring Boot applications is also easy; you don’t need any special IDE plugins or extensions.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| This section only covers jar based packaging, If you choose to package your application as a war file you should refer to your server and IDE documentation. |
+
+## 19.1 Running from an IDE
+
+You can run a Spring Boot application from your IDE as a simple Java application, however, first you will need to import your project. Import steps will vary depending on your IDE and build system. Most IDEs can import Maven projects directly, for example Eclipse users can select `Import…` → `Existing Maven Projects` from the `File` menu.
+
+If you can’t directly import your project into your IDE, you may be able to generate IDE metadata using a build plugin. Maven includes plugins for [Eclipse](https://maven.apache.org/plugins/maven-eclipse-plugin/) and [IDEA](https://maven.apache.org/plugins/maven-idea-plugin/); Gradle offers plugins for [various IDEs](https://docs.gradle.org/3.4.1/userguide/userguide.html).
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| If you accidentally run a web application twice you will see a “Port already in use” error. STS users can use the `Relaunch` button rather than `Run` to ensure that any existing instance is closed. |
+
+## 19.2 Running as a packaged application
+
+If you use the Spring Boot Maven or Gradle plugins to create an executable jar you can run your application using `java -jar`. For example:
+
+```
+$ java -jar target/myproject-0.0.1-SNAPSHOT.jar
+
+```
+
+It is also possible to run a packaged application with remote debugging support enabled. This allows you to attach a debugger to your packaged application:
+
+```
+$ java -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=8000,suspend=n \
+ -jar target/myproject-0.0.1-SNAPSHOT.jar
+
+```
+
+## 19.3 Using the Maven plugin
+
+The Spring Boot Maven plugin includes a `run` goal which can be used to quickly compile and run your application. Applications run in an exploded form just like in your IDE.
+
+```
+$ mvn spring-boot:run
+
+```
+
+You might also want to use the useful operating system environment variable:
+
+```
+$ export MAVEN_OPTS=-Xmx1024m
+
+```
+
+## 19.4 Using the Gradle plugin
+
+The Spring Boot Gradle plugin also includes a `bootRun` task which can be used to run your application in an exploded form. The `bootRun` task is added whenever you apply the the `org.springframework.boot` and `java` plugins:
+
+```
+$ gradle bootRun
+
+```
+
+You might also want to use this useful operating system environment variable:
+
+```
+$ export JAVA_OPTS=-Xmx1024m
+
+```
+
+## 19.5 Hot swapping
+
+Since Spring Boot applications are just plain Java applications, JVM hot-swapping should work out of the box. JVM hot swapping is somewhat limited with the bytecode that it can replace, for a more complete solution [JRebel](http://zeroturnaround.com/software/jrebel/) can be used. The `spring-boot-devtools` module also includes support for quick application restarts.
+
+See the [Chapter 20, *Developer tools*](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools) section below and the [Hot swapping “How-to”](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-hotswapping) for details.
+
+## 20. Developer tools
+
+Spring Boot includes an additional set of tools that can make the application development experience a little more pleasant. The `spring-boot-devtools` module can be included in any project to provide additional development-time features. To include devtools support, simply add the module dependency to your build:
+
+**Maven.**
+
+```
+
+
+ org.springframework.boot
+ spring-boot-devtools
+ true
+
+
+
+```
+
+
+
+**Gradle.**
+
+```
+dependencies {
+ compile("org.springframework.boot:spring-boot-devtools")
+}
+
+```
+
+
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Developer tools are automatically disabled when running a fully packaged application. If your application is launched using `java -jar` or if it’s started using a special classloader, then it is considered a “production application”. Flagging the dependency as optional is a best practice that prevents devtools from being transitively applied to other modules using your project. Gradle does not support `optional` dependencies out-of-the-box so you may want to have a look to the [`propdeps-plugin`](https://github.com/spring-projects/gradle-plugins/tree/master/propdeps-plugin) in the meantime. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| repackaged archives do not contain devtools by default. If you want to use [certain remote devtools feature](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-remote), you’ll need to disable the `excludeDevtools`build property to include it. The property is supported with both the Maven and Gradle plugins. |
+
+## 20.1 Property defaults
+
+Several of the libraries supported by Spring Boot use caches to improve performance. For example, [template engines](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-spring-mvc-template-engines) will cache compiled templates to avoid repeatedly parsing template files. Also, Spring MVC can add HTTP caching headers to responses when serving static resources.
+
+Whilst caching is very beneficial in production, it can be counter productive during development, preventing you from seeing the changes you just made in your application. For this reason, spring-boot-devtools will disable those caching options by default.
+
+Cache options are usually configured by settings in your `application.properties` file. For example, Thymeleaf offers the `spring.thymeleaf.cache` property. Rather than needing to set these properties manually, the `spring-boot-devtools` module will automatically apply sensible development-time configuration.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| For a complete list of the properties that are applied see [DevToolsPropertyDefaultsPostProcessor](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-devtools/src/main/java/org/springframework/boot/devtools/env/DevToolsPropertyDefaultsPostProcessor.java). |
+
+## 20.2 Automatic restart
+
+Applications that use `spring-boot-devtools` will automatically restart whenever files on the classpath change. This can be a useful feature when working in an IDE as it gives a very fast feedback loop for code changes. By default, any entry on the classpath that points to a folder will be monitored for changes. Note that certain resources such as static assets and view templates [do not need to restart the application](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-exclude).
+
+**Triggering a restart**
+
+As DevTools monitors classpath resources, the only way to trigger a restart is to update the classpath. The way in which you cause the classpath to be updated depends on the IDE that you are using. In Eclipse, saving a modified file will cause the classpath to be updated and trigger a restart. In IntelliJ IDEA, building the project (`Build -> Make Project`) will have the same effect.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| You can also start your application via the supported build plugins (i.e. Maven and Gradle) as long as forking is enabled since DevTools need an isolated application classloader to operate properly. Gradle and Maven do that by default when they detect DevTools on the classpath. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Automatic restart works very well when used with LiveReload. [See below](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-livereload) for details. If you use JRebel automatic restarts will be disabled in favor of dynamic class reloading. Other devtools features (such as LiveReload and property overrides) can still be used. |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| DevTools relies on the application context’s shutdown hook to close it during a restart. It will not work correctly if you have disabled the shutdown hook (`SpringApplication.setRegisterShutdownHook(false)`). |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| When deciding if an entry on the classpath should trigger a restart when it changes, DevTools automatically ignores projects named `spring-boot`, `spring-boot-devtools`, `spring-boot-autoconfigure`, `spring-boot-actuator`, and `spring-boot-starter`. |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| DevTools needs to customize the `ResourceLoader` used by the `ApplicationContext`: if your application provides one already, it is going to be wrapped. Direct override of the `getResource` method on the `ApplicationContext` is not supported. |
+
+
+
+**Restart vs Reload**
+
+The restart technology provided by Spring Boot works by using two classloaders. Classes that don’t change (for example, those from third-party jars) are loaded into a *base* classloader. Classes that you’re actively developing are loaded into a *restart* classloader. When the application is restarted, the *restart* classloader is thrown away and a new one is created. This approach means that application restarts are typically much faster than “cold starts” since the *base* classloader is already available and populated.
+
+If you find that restarts aren’t quick enough for your applications, or you encounter classloading issues, you could consider reloading technologies such as [JRebel](http://zeroturnaround.com/software/jrebel/)from ZeroTurnaround. These work by rewriting classes as they are loaded to make them more amenable to reloading.
+
+### 20.2.1 Excluding resources
+
+Certain resources don’t necessarily need to trigger a restart when they are changed. For example, Thymeleaf templates can just be edited in-place. By default changing resources in `/META-INF/maven`, `/META-INF/resources` ,`/resources` ,`/static` ,`/public` or `/templates` will not trigger a restart but will trigger a [live reload](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-livereload). If you want to customize these exclusions you can use the `spring.devtools.restart.exclude` property. For example, to exclude only `/static` and `/public` you would set the following:
+
+```
+spring.devtools.restart.exclude=static/**,public/**
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| if you want to keep those defaults and *add* additional exclusions, use the `spring.devtools.restart.additional-exclude` property instead. |
+
+### 20.2.2 Watching additional paths
+
+You may want your application to be restarted or reloaded when you make changes to files that are not on the classpath. To do so, use the`spring.devtools.restart.additional-paths` property to configure additional paths to watch for changes. You can use the `spring.devtools.restart.exclude` property [described above](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-exclude) to control whether changes beneath the additional paths will trigger a full restart or just a [live reload](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-livereload).
+
+### 20.2.3 Disabling restart
+
+If you don’t want to use the restart feature you can disable it using the `spring.devtools.restart.enabled` property. In most cases you can set this in your`application.properties` (this will still initialize the restart classloader but it won’t watch for file changes).
+
+If you need to *completely* disable restart support, for example, because it doesn’t work with a specific library, you need to set a `System` property before calling`SpringApplication.run(…)`. For example:
+
+```
+public static void main(String[] args) {
+ System.setProperty("spring.devtools.restart.enabled", "false");
+ SpringApplication.run(MyApp.class, args);
+}
+
+```
+
+### 20.2.4 Using a trigger file
+
+If you work with an IDE that continuously compiles changed files, you might prefer to trigger restarts only at specific times. To do this you can use a “trigger file”, which is a special file that must be modified when you want to actually trigger a restart check. Changing the file only triggers the check and the restart will only occur if Devtools has detected it has to do something. The trigger file could be updated manually, or via an IDE plugin.
+
+To use a trigger file use the `spring.devtools.restart.trigger-file` property.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| You might want to set `spring.devtools.restart.trigger-file` as a [global setting](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-globalsettings) so that all your projects behave in the same way. |
+
+### 20.2.5 Customizing the restart classloader
+
+As described in the [Restart vs Reload](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-spring-boot-restart-vs-reload) section above, restart functionality is implemented by using two classloaders. For most applications this approach works well, however, sometimes it can cause classloading issues.
+
+By default, any open project in your IDE will be loaded using the “restart” classloader, and any regular `.jar` file will be loaded using the “base” classloader. If you work on a multi-module project, and not each module is imported into your IDE, you may need to customize things. To do this you can create a `META-INF/spring-devtools.properties` file.
+
+The `spring-devtools.properties` file can contain `restart.exclude.` and `restart.include.` prefixed properties. 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 will be applied to the classpath.
+
+For example:
+
+```
+restart.exclude.companycommonlibs=/mycorp-common-[\\w-]+\.jar
+restart.include.projectcommon=/mycorp-myproj-[\\w-]+\.jar
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| All property keys must be unique. As long as a property starts with `restart.include.` or `restart.exclude.` it will be considered. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| All `META-INF/spring-devtools.properties` from the classpath will be loaded. You can package files inside your project, or in the libraries that the project consumes. |
+
+### 20.2.6 Known limitations
+
+Restart functionality does not work well with objects that are deserialized using a standard `ObjectInputStream`. If you need to deserialize data, you may need to use Spring’s `ConfigurableObjectInputStream` in combination with `Thread.currentThread().getContextClassLoader()`.
+
+Unfortunately, several third-party libraries deserialize without considering the context classloader. If you find such a problem, you will need to request a fix with the original authors.
+
+## 20.3 LiveReload
+
+The `spring-boot-devtools` module includes an embedded LiveReload server that can be used to trigger a browser refresh when a resource is changed. LiveReload browser extensions are freely available for Chrome, Firefox and Safari from [livereload.com](http://livereload.com/extensions/).
+
+If you don’t want to start the LiveReload server when your application runs you can set the `spring.devtools.livereload.enabled` property to `false`.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| You can only run one LiveReload server at a time. Before starting your application, ensure that no other LiveReload servers are running. If you start multiple applications from your IDE, only the first will have LiveReload support. |
+
+## 20.4 Global settings
+
+You can configure global devtools settings by adding a file named `.spring-boot-devtools.properties` to your `$HOME` folder (note that the filename starts with “.”). Any properties added to this file will apply to *all* Spring Boot applications on your machine that use devtools. For example, to configure restart to always use a [trigger file](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart-triggerfile), you would add the following:
+
+**~/.spring-boot-devtools.properties.**
+
+```
+spring.devtools.reload.trigger-file=.reloadtrigger
+
+```
+
+
+
+## 20.5 Remote applications
+
+The Spring Boot developer tools are not just limited to local development. You can also use several features when running applications remotely. Remote support is opt-in, to enable it you need to make sure that `devtools` is included in the repackaged archive:
+
+```
+
+
+
+ org.springframework.boot
+ spring-boot-maven-plugin
+
+ false
+
+
+
+
+
+```
+
+Then you need to set a `spring.devtools.remote.secret` property, for example:
+
+```
+spring.devtools.remote.secret=mysecret
+
+```
+
+| ![[Warning]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/warning.png) |
+| ------------------------------------------------------------ |
+| Enabling `spring-boot-devtools` on a remote application is a security risk. You should never enable support on a production deployment. |
+
+Remote devtools support is provided in two parts; there is a server side endpoint that accepts connections, and a client application that you run in your IDE. The server component is automatically enabled when the `spring.devtools.remote.secret` property is set. The client component must be launched manually.
+
+### 20.5.1 Running the remote client application
+
+The remote client application is designed to be run from within your IDE. You need to run `org.springframework.boot.devtools.RemoteSpringApplication`using the same classpath as the remote project that you’re connecting to. The *non-option* argument passed to the application should be the remote URL that you are connecting to.
+
+For example, if you are using Eclipse or STS, and you have a project named `my-app` that you’ve deployed to Cloud Foundry, you would do the following:
+
+- Select `Run Configurations…` from the `Run` menu.
+- Create a new `Java Application` “launch configuration”.
+- Browse for the `my-app` project.
+- Use `org.springframework.boot.devtools.RemoteSpringApplication` as the main class.
+- Add `https://myapp.cfapps.io` to the `Program arguments` (or whatever your remote URL is).
+
+A running remote client will look like this:
+
+```
+ . ____ _ __ _ _
+ /\\ / ___'_ __ _ _(_)_ __ __ _ ___ _ \ \ \ \
+( ( )\___ | '_ | '_| | '_ \/ _` | | _ \___ _ __ ___| |_ ___ \ \ \ \
+ \\/ ___)| |_)| | | | | || (_| []::::::[] / -_) ' \/ _ \ _/ -_) ) ) ) )
+ ' |____| .__|_| |_|_| |_\__, | |_|_\___|_|_|_\___/\__\___|/ / / /
+ =========|_|==============|___/===================================/_/_/_/
+ :: Spring Boot Remote :: 2.0.0.M3
+
+2015-06-10 18:25:06.632 INFO 14938 --- [ main] o.s.b.devtools.RemoteSpringApplication : Starting RemoteSpringApplication on pwmbp with PID 14938 (/Users/pwebb/projects/spring-boot/code/spring-boot-devtools/target/classes started by pwebb in /Users/pwebb/projects/spring-boot/code/spring-boot-samples/spring-boot-sample-devtools)
+2015-06-10 18:25:06.671 INFO 14938 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@2a17b7b6: startup date [Wed Jun 10 18:25:06 PDT 2015]; root of context hierarchy
+2015-06-10 18:25:07.043 WARN 14938 --- [ main] o.s.b.d.r.c.RemoteClientConfiguration : The connection to http://localhost:8080 is insecure. You should use a URL starting with 'https://'.
+2015-06-10 18:25:07.074 INFO 14938 --- [ main] o.s.b.d.a.OptionalLiveReloadServer : LiveReload server is running on port 35729
+2015-06-10 18:25:07.130 INFO 14938 --- [ main] o.s.b.devtools.RemoteSpringApplication : Started RemoteSpringApplication in 0.74 seconds (JVM running for 1.105)
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Because the remote client is using the same classpath as the real application it can directly read application properties. This is how the `spring.devtools.remote.secret` property is read and passed to the server for authentication. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| It’s always advisable to use `https://` as the connection protocol so that traffic is encrypted and passwords cannot be intercepted. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| If you need to use a proxy to access the remote application, configure the `spring.devtools.remote.proxy.host` and `spring.devtools.remote.proxy.port` properties. |
+
+### 20.5.2 Remote update
+
+The remote client will monitor your application classpath for changes in the same way as the [local restart](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-restart). Any updated resource will be pushed to the remote application and *(if required)* trigger a restart. This can be quite helpful if you are iterating on a feature that uses a cloud service that you don’t have locally. Generally remote updates and restarts are much quicker than a full rebuild and deploy cycle.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Files are only monitored when the remote client is running. If you change a file before starting the remote client, it won’t be pushed to the remote server. |
+
+## 21. Packaging your application for production
+
+Executable jars can be used for production deployment. As they are self-contained, they are also ideally suited for cloud-based deployment.
+
+For additional “production ready” features, such as health, auditing and metric REST or JMX end-points; consider adding `spring-boot-actuator`. See *Part V, “Spring Boot Actuator: Production-ready features”* for details.
+
+## 22. What to read next
+
+You should now have good understanding of how you can use Spring Boot along with some best practices that you should follow. You can now go on to learn about specific *Spring Boot features* in depth, or you could skip ahead and read about the “[production ready](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#production-ready)” aspects of Spring Boot.
+
+# Part IV. Spring Boot features
+
+
+
+This section dives into the details of Spring Boot. Here you can learn about the key features that you will want to use and customize. If you haven’t already, you might want to read the *Part II, “Getting started”* and *Part III, “Using Spring Boot”* sections so that you have a good grounding of the basics.
+
+## 23. SpringApplication
+
+The `SpringApplication` class provides a convenient way to bootstrap a Spring application that will be started from a `main()` method. In many situations you can just delegate to the static `SpringApplication.run` method:
+
+```
+public static void main(String[] args) {
+ SpringApplication.run(MySpringConfiguration.class, args);
+}
+
+```
+
+When your application starts you should see something similar to the following:
+
+```
+ . ____ _ __ _ _
+ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
+( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
+ \\/ ___)| |_)| | | | | || (_| | ) ) ) )
+ ' |____| .__|_| |_|_| |_\__, | / / / /
+ =========|_|==============|___/=/_/_/_/
+ :: Spring Boot :: v2.0.0.M3
+
+2013-07-31 00:08:16.117 INFO 56603 --- [ main] o.s.b.s.app.SampleApplication : Starting SampleApplication v0.1.0 on mycomputer with PID 56603 (/apps/myapp.jar started by pwebb)
+2013-07-31 00:08:16.166 INFO 56603 --- [ main] ationConfigServletWebServerApplicationContext : Refreshing org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@6e5a8246: startup date [Wed Jul 31 00:08:16 PDT 2013]; root of context hierarchy
+2014-03-04 13:09:54.912 INFO 41370 --- [ main] .t.TomcatServletWebServerFactory : Server initialized with port: 8080
+2014-03-04 13:09:56.501 INFO 41370 --- [ main] o.s.b.s.app.SampleApplication : Started SampleApplication in 2.992 seconds (JVM running for 3.658)
+
+```
+
+By default `INFO` logging messages will be shown, including some relevant startup details such as the user that launched the application.
+
+## 23.1 Startup failure
+
+If your application fails to start, registered `FailureAnalyzers` get a chance to provide a dedicated error message and a concrete action to fix the problem. For instance if you start a web application on port `8080` and that port is already in use, you should see something similar to the following:
+
+```
+***************************
+APPLICATION FAILED TO START
+***************************
+
+Description:
+
+Embedded servlet container failed to start. Port 8080 was already in use.
+
+Action:
+
+Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Spring Boot provides numerous `FailureAnalyzer` implementations and you can [add your own](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-failure-analyzer) very easily. |
+
+If no failure analyzers are able to handle the exception, you can still display the full auto-configuration report to better understand what went wrong. To do so you need to[enable the `debug` property](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config) or [enable `DEBUG` logging](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-custom-log-levels) for`org.springframework.boot.autoconfigure.logging.AutoConfigurationReportLoggingInitializer`.
+
+For instance, if you are running your application using `java -jar` you can enable the `debug` property as follows:
+
+```
+$ java -jar myproject-0.0.1-SNAPSHOT.jar --debug
+
+```
+
+## 23.2 Customizing the Banner
+
+The banner that is printed on start up can be changed by adding a `banner.txt` file to your classpath, or by setting `banner.location` to the location of such a file. If the file has an unusual encoding you can set `banner.charset` (default is `UTF-8`). In addition to a text file, you can also add a `banner.gif`, `banner.jpg` or `banner.png` image file to your classpath, or set a `banner.image.location` property. Images will be converted into an ASCII art representation and printed above any text banner.
+
+Inside your `banner.txt` file you can use any of the following placeholders:
+
+
+
+**Table 23.1. Banner variables**
+
+| Variable | Description |
+| ------------------------------------------------------------ | ------------------------------------------------------------ |
+| `${application.version}` | The version number of your application as declared in `MANIFEST.MF`. For example`Implementation-Version: 1.0` is printed as `1.0`. |
+| `${application.formatted-version}` | The version number of your application as declared in `MANIFEST.MF` formatted for display (surrounded with brackets and prefixed with `v`). For example `(v1.0)`. |
+| `${spring-boot.version}` | The Spring Boot version that you are using. For example `2.0.0.M3`. |
+| `${spring-boot.formatted-version}` | The Spring Boot version that you are using formatted for display (surrounded with brackets and prefixed with `v`). For example `(v2.0.0.M3)`. |
+| `${Ansi.NAME}` (or `${AnsiColor.NAME}`, `${AnsiBackground.NAME}`, `${AnsiStyle.NAME}`) | Where `NAME` is the name of an ANSI escape code. See [`AnsiPropertySource`](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot/src/main/java/org/springframework/boot/ansi/AnsiPropertySource.java) for details. |
+| `${application.title}` | The title of your application as declared in `MANIFEST.MF`. For example`Implementation-Title: MyApp` is printed as `MyApp`. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The `SpringApplication.setBanner(…)` method can be used if you want to generate a banner programmatically. Use the `org.springframework.boot.Banner` interface and implement your own `printBanner()` method. |
+
+You can also use the `spring.main.banner-mode` property to determine if the banner has to be printed on `System.out` (`console`), using the configured logger (`log`) or not at all (`off`).
+
+The printed banner will be registered as a singleton bean under the name `springBootBanner`.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| YAML maps `off` to `false` so make sure to add quotes if you want to disable the banner in your application.`spring: main: banner-mode: "off"` |
+
+## 23.3 Customizing SpringApplication
+
+If the `SpringApplication` defaults aren’t to your taste you can instead create a local instance and customize it. For example, to turn off the banner you would write:
+
+```
+public static void main(String[] args) {
+ SpringApplication app = new SpringApplication(MySpringConfiguration.class);
+ app.setBannerMode(Banner.Mode.OFF);
+ app.run(args);
+}
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| The constructor arguments passed to `SpringApplication` are configuration sources for spring beans. In most cases these will be references to `@Configuration` classes, but they could also be references to XML configuration or to packages that should be scanned. |
+
+It is also possible to configure the `SpringApplication` using an `application.properties` file. See *Chapter 24, Externalized Configuration* for details.
+
+For a complete list of the configuration options, see the [`SpringApplication` Javadoc](https://docs.spring.io/spring-boot/docs/2.0.0.M3/api/org/springframework/boot/SpringApplication.html).
+
+## 23.4 Fluent builder API
+
+If you need to build an `ApplicationContext` hierarchy (multiple contexts with a parent/child relationship), or if you just prefer using a ‘fluent’ builder API, you can use the `SpringApplicationBuilder`.
+
+The `SpringApplicationBuilder` allows you to chain together multiple method calls, and includes `parent` and `child` methods that allow you to create a hierarchy.
+
+For example:
+
+```
+new SpringApplicationBuilder()
+ .sources(Parent.class)
+ .child(Application.class)
+ .bannerMode(Banner.Mode.OFF)
+ .run(args);
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| There are some restrictions when creating an `ApplicationContext` hierarchy, e.g. Web components **must** be contained within the child context, and the same `Environment` will be used for both parent and child contexts. See the [`SpringApplicationBuilder` Javadoc](https://docs.spring.io/spring-boot/docs/2.0.0.M3/api/org/springframework/boot/builder/SpringApplicationBuilder.html) for full details. |
+
+## 23.5 Application events and listeners
+
+In addition to the usual Spring Framework events, such as [`ContextRefreshedEvent`](https://docs.spring.io/spring/docs/5.0.0.RC3/javadoc-api/org/springframework/context/event/ContextRefreshedEvent.html), a `SpringApplication` sends some additional application events.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Some events are actually triggered before the `ApplicationContext` is created so you cannot register a listener on those as a `@Bean`. You can register them via the `SpringApplication.addListeners(…)` or `SpringApplicationBuilder.listeners(…)` methods.If you want those listeners to be registered automatically regardless of the way the application is created you can add a `META-INF/spring.factories`file to your project and reference your listener(s) using the `org.springframework.context.ApplicationListener` key.`org.springframework.context.ApplicationListener=com.example.project.MyListener` |
+
+Application events are sent in the following order, as your application runs:
+
+1. An `ApplicationStartingEvent` is sent at the start of a run, but before any processing except the registration of listeners and initializers.
+2. An `ApplicationEnvironmentPreparedEvent` is sent when the `Environment` to be used in the context is known, but before the context is created.
+3. An `ApplicationPreparedEvent` is sent just before the refresh is started, but after bean definitions have been loaded.
+4. An `ApplicationReadyEvent` is sent after the refresh and any related callbacks have been processed to indicate the application is ready to service requests.
+5. An `ApplicationFailedEvent` is sent if there is an exception on startup.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| You often won’t need to use application events, but it can be handy to know that they exist. Internally, Spring Boot uses events to handle a variety of tasks. |
+
+## 23.6 Web environment
+
+A `SpringApplication` will attempt to create the right type of `ApplicationContext` on your behalf. By default, an `AnnotationConfigApplicationContext`or `AnnotationConfigServletWebServerApplicationContext` will be used, depending on whether you are developing a web application or not.
+
+The algorithm used to determine a ‘web environment’ is fairly simplistic (based on the presence of a few classes). You can use `setWebEnvironment(boolean webEnvironment)` if you need to override the default.
+
+It is also possible to take complete control of the `ApplicationContext` type that will be used by calling `setApplicationContextClass(…)`.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| It is often desirable to call `setWebEnvironment(false)` when using `SpringApplication` within a JUnit test. |
+
+## 23.7 Accessing application arguments
+
+If you need to access the application arguments that were passed to `SpringApplication.run(…)` you can inject a`org.springframework.boot.ApplicationArguments` bean. The `ApplicationArguments` interface provides access to both the raw `String[]` arguments as well as parsed `option` and `non-option` arguments:
+
+```
+import org.springframework.boot.*
+import org.springframework.beans.factory.annotation.*
+import org.springframework.stereotype.*
+
+@Component
+public class MyBean {
+
+ @Autowired
+ public MyBean(ApplicationArguments args) {
+ boolean debug = args.containsOption("debug");
+ List files = args.getNonOptionArgs();
+ // if run with "--debug logfile.txt" debug=true, files=["logfile.txt"]
+ }
+
+}
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Spring Boot will also register a `CommandLinePropertySource` with the Spring `Environment`. This allows you to also inject single application arguments using the `@Value` annotation. |
+
+## 23.8 Using the ApplicationRunner or CommandLineRunner
+
+If you need to run some specific code once the `SpringApplication` has started, you can implement the `ApplicationRunner` or `CommandLineRunner`interfaces. Both interfaces work in the same way and offer a single `run` method which will be called just before `SpringApplication.run(…)` completes.
+
+The `CommandLineRunner` interfaces provides access to application arguments as a simple string array, whereas the `ApplicationRunner` uses the `ApplicationArguments` interface discussed above.
+
+```
+import org.springframework.boot.*
+import org.springframework.stereotype.*
+
+@Component
+public class MyBean implements CommandLineRunner {
+
+ public void run(String... args) {
+ // Do something...
+ }
+
+}
+
+```
+
+You can additionally implement the `org.springframework.core.Ordered` interface or use the `org.springframework.core.annotation.Order` annotation if several `CommandLineRunner` or `ApplicationRunner` beans are defined that must be called in a specific order.
+
+## 23.9 Application exit
+
+Each `SpringApplication` will register a shutdown hook with the JVM to ensure that the `ApplicationContext` is closed gracefully on exit. All the standard Spring lifecycle callbacks (such as the `DisposableBean` interface, or the `@PreDestroy` annotation) can be used.
+
+In addition, beans may implement the `org.springframework.boot.ExitCodeGenerator` interface if they wish to return a specific exit code when `SpringApplication.exit()` is called. This exit code can then be passed to `System.exit()` to return it as a status code.
+
+```
+@SpringBootApplication
+public class ExitCodeApplication {
+
+ @Bean
+ public ExitCodeGenerator exitCodeGenerator() {
+ return () -> 42;
+ }
+
+ public static void main(String[] args) {
+ System.exit(SpringApplication
+ .exit(SpringApplication.run(ExitCodeApplication.class, args)));
+ }
+
+}
+
+```
+
+Also, the `ExitCodeGenerator` interface may be implemented by exceptions. When such an exception is encountered, Spring Boot will return the exit code provided by the implemented `getExitCode()` method.
+
+## 23.10 Admin features
+
+It is possible to enable admin-related features for the application by specifying the `spring.application.admin.enabled` property. This exposes the[`SpringApplicationAdminMXBean`](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot/src/main/java/org/springframework/boot/admin/SpringApplicationAdminMXBean.java) on the platform `MBeanServer`. You could use this feature to administer your Spring Boot application remotely. This could also be useful for any service wrapper implementation.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| If you want to know on which HTTP port the application is running, get the property with key `local.server.port`. |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Take care when enabling this feature as the MBean exposes a method to shutdown the application. |
+
+## 24. Externalized Configuration
+
+Spring Boot allows you to externalize your configuration so you can work with the same application code in different environments. You can use properties files, YAML files, environment variables and command-line arguments to externalize configuration. Property values can be injected directly into your beans using the `@Value`annotation, accessed via Spring’s `Environment` abstraction or [bound to structured objects](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-typesafe-configuration-properties) via `@ConfigurationProperties`.
+
+Spring Boot uses a very particular `PropertySource` order that is designed to allow sensible overriding of values. Properties are considered in the following order:
+
+1. [Devtools global settings properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#using-boot-devtools-globalsettings) on your home directory (`~/.spring-boot-devtools.properties` when devtools is active).
+2. [`@TestPropertySource`](https://docs.spring.io/spring/docs/5.0.0.RC3/javadoc-api/org/springframework/test/context/TestPropertySource.html) annotations on your tests.
+3. [`@SpringBootTest#properties`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/api/org/springframework/boot/test/context/SpringBootTest.html) annotation attribute on your tests.
+4. Command line arguments.
+5. Properties from `SPRING_APPLICATION_JSON` (inline JSON embedded in an environment variable or system property)
+6. `ServletConfig` init parameters.
+7. `ServletContext` init parameters.
+8. JNDI attributes from `java:comp/env`.
+9. Java System properties (`System.getProperties()`).
+10. OS environment variables.
+11. A `RandomValuePropertySource` that only has properties in `random.*`.
+12. [Profile-specific application properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-profile-specific-properties) outside of your packaged jar (`application-{profile}.properties` and YAML variants)
+13. [Profile-specific application properties](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-profile-specific-properties) packaged inside your jar (`application-{profile}.properties` and YAML variants)
+14. Application properties outside of your packaged jar (`application.properties` and YAML variants).
+15. Application properties packaged inside your jar (`application.properties` and YAML variants).
+16. [`@PropertySource`](https://docs.spring.io/spring/docs/5.0.0.RC3/javadoc-api/org/springframework/context/annotation/PropertySource.html) annotations on your `@Configuration` classes.
+17. Default properties (specified using `SpringApplication.setDefaultProperties`).
+
+To provide a concrete example, suppose you develop a `@Component` that uses a `name` property:
+
+```
+import org.springframework.stereotype.*
+import org.springframework.beans.factory.annotation.*
+
+@Component
+public class MyBean {
+
+ @Value("${name}")
+ private String name;
+
+ // ...
+
+}
+
+```
+
+On your application classpath (e.g. inside your jar) you can have an `application.properties` that provides a sensible default property value for `name`. When running in a new environment, an `application.properties` can be provided outside of your jar that overrides the `name`; and for one-off testing, you can launch with a specific command line switch (e.g. `java -jar app.jar --name="Spring"`).
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The `SPRING_APPLICATION_JSON` properties can be supplied on the command line with an environment variable. For example in a UN*X shell:`$ SPRING_APPLICATION_JSON='{"foo":{"bar":"spam"}}' java -jar myapp.jar`In this example you will end up with `foo.bar=spam` in the Spring `Environment`. You can also supply the JSON as `spring.application.json` in a System variable:`$ java -Dspring.application.json='{"foo":"bar"}' -jar myapp.jar`or command line argument:`$ java -jar myapp.jar --spring.application.json='{"foo":"bar"}'`or as a JNDI variable `java:comp/env/spring.application.json`. |
+
+## 24.1 Configuring random values
+
+The `RandomValuePropertySource` is useful for injecting random values (e.g. into secrets or test cases). It can produce integers, longs, uuids or strings, e.g.
+
+```
+my.secret=${random.value}
+my.number=${random.int}
+my.bignumber=${random.long}
+my.uuid=${random.uuid}
+my.number.less.than.ten=${random.int(10)}
+my.number.in.range=${random.int[1024,65536]}
+
+```
+
+The `random.int*` syntax is `OPEN value (,max) CLOSE` where the `OPEN,CLOSE` are any character and `value,max` are integers. If `max` is provided then `value` is the minimum value and `max` is the maximum (exclusive).
+
+## 24.2 Accessing command line properties
+
+By default `SpringApplication` will convert any command line option arguments (starting with ‘--’, e.g. `--server.port=9000`) to a `property` and add it to the Spring `Environment`. As mentioned above, command line properties always take precedence over other property sources.
+
+If you don’t want command line properties to be added to the `Environment` you can disable them using `SpringApplication.setAddCommandLineProperties(false)`.
+
+## 24.3 Application property files
+
+`SpringApplication` will load properties from `application.properties` files in the following locations and add them to the Spring `Environment`:
+
+1. A `/config` subdirectory of the current directory.
+2. The current directory
+3. A classpath `/config` package
+4. The classpath root
+
+The list is ordered by precedence (properties defined in locations higher in the list override those defined in lower locations).
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| You can also [use YAML ('.yml') files](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-yaml) as an alternative to '.properties'. |
+
+If you don’t like `application.properties` as the configuration file name you can switch to another by specifying a `spring.config.name` environment property. You can also refer to an explicit location using the `spring.config.location` environment property (comma-separated list of directory locations, or file paths).
+
+```
+$ java -jar myproject.jar --spring.config.name=myproject
+
+```
+
+or
+
+```
+$ java -jar myproject.jar --spring.config.location=classpath:/default.properties,classpath:/override.properties
+
+```
+
+| ![[Warning]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/warning.png) |
+| ------------------------------------------------------------ |
+| `spring.config.name` and `spring.config.location` are used very early to determine which files have to be loaded so they have to be defined as an environment property (typically OS env, system property or command line argument). |
+
+If `spring.config.location` contains directories (as opposed to files) they should end in `/` (and will be appended with the names generated from `spring.config.name` before being loaded, including profile-specific file names). Files specified in `spring.config.location` are used as-is, with no support for profile-specific variants, and will be overridden by any profile-specific properties.
+
+Config locations are searched in reverse order. By default, the configured locations are `classpath:/,classpath:/config/,file:./,file:./config/`. The resulting search order is:
+
+1. `file:./config/`
+2. `file:./`
+3. `classpath:/config/`
+4. `classpath:/`
+
+When custom config locations are configured, they are used in addition to the default locations. Custom locations are searched before the default locations. For example, if custom locations `classpath:/custom-config/,file:./custom-config/` are configured, the search order becomes:
+
+1. `file:./custom-config/`
+2. `classpath:custom-config/`
+3. `file:./config/`
+4. `file:./`
+5. `classpath:/config/`
+6. `classpath:/`
+
+This search ordering allows you to specify default values in one configuration file and then selectively override those values in another. You can provide default values for you application in `application.properties` (or whatever other basename you choose with `spring.config.name`) in one of the default locations. These default values can then be overriden at runtime with a different file located in one of the custom locations.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you use environment variables rather than system properties, most operating systems disallow period-separated key names, but you can use underscores instead (e.g. `SPRING_CONFIG_NAME` instead of `spring.config.name`). |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you are running in a container then JNDI properties (in `java:comp/env`) or servlet context initialization parameters can be used instead of, or as well as, environment variables or system properties. |
+
+## 24.4 Profile-specific properties
+
+In addition to `application.properties` files, profile-specific properties can also be defined using the naming convention `application-{profile}.properties`. The `Environment` has a set of default profiles (by default `[default]`) which are used if no active profiles are set (i.e. if no profiles are explicitly activated then properties from `application-default.properties` are loaded).
+
+Profile-specific properties are loaded from the same locations as standard `application.properties`, with profile-specific files always overriding the non-specific ones irrespective of whether the profile-specific files are inside or outside your packaged jar.
+
+If several profiles are specified, a last wins strategy applies. For example, profiles specified by the `spring.profiles.active` property are added after those configured via the `SpringApplication` API and therefore take precedence.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you have specified any files in `spring.config.location`, profile-specific variants of those files will not be considered. Use directories in`spring.config.location` if you also want to also use profile-specific properties. |
+
+## 24.5 Placeholders in properties
+
+The values in `application.properties` are filtered through the existing `Environment` when they are used so you can refer back to previously defined values (e.g. from System properties).
+
+```
+app.name=MyApp
+app.description=${app.name} is a Spring Boot application
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| You can also use this technique to create ‘short’ variants of existing Spring Boot properties. See the *Section 73.4, “Use ‘short’ command line arguments”*how-to for details. |
+
+## 24.6 Using YAML instead of Properties
+
+[YAML](http://yaml.org/) is a superset of JSON, and as such is a very convenient format for specifying hierarchical configuration data. The `SpringApplication` class will automatically support YAML as an alternative to properties whenever you have the [SnakeYAML](http://www.snakeyaml.org/) library on your classpath.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you use ‘Starters’ SnakeYAML will be automatically provided via `spring-boot-starter`. |
+
+### 24.6.1 Loading YAML
+
+Spring Framework provides two convenient classes that can be used to load YAML documents. The `YamlPropertiesFactoryBean` will load YAML as `Properties`and the `YamlMapFactoryBean` will load YAML as a `Map`.
+
+For example, the following YAML document:
+
+```
+environments:
+ dev:
+ url: http://dev.bar.com
+ name: Developer Setup
+ prod:
+ url: http://foo.bar.com
+ name: My Cool App
+
+```
+
+Would be transformed into these properties:
+
+```
+environments.dev.url=http://dev.bar.com
+environments.dev.name=Developer Setup
+environments.prod.url=http://foo.bar.com
+environments.prod.name=My Cool App
+
+```
+
+YAML lists are represented as property keys with `[index]` dereferencers, for example this YAML:
+
+```
+my:
+ servers:
+ - dev.bar.com
+ - foo.bar.com
+
+```
+
+Would be transformed into these properties:
+
+```
+my.servers[0]=dev.bar.com
+my.servers[1]=foo.bar.com
+
+```
+
+To bind to properties like that using the Spring `DataBinder` utilities (which is what `@ConfigurationProperties` does) you need to have a property in the target bean of type `java.util.List` (or `Set`) and you either need to provide a setter, or initialize it with a mutable value, e.g. this will bind to the properties above
+
+```
+@ConfigurationProperties(prefix="my")
+public class Config {
+
+ private List servers = new ArrayList();
+
+ public List getServers() {
+ return this.servers;
+ }
+}
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Extra care is required when configuring lists that way as overriding will not work as you would expect. In the example above, when `my.servers` is redefined in several places, the individual elements are targeted for override, not the list. To make sure that a `PropertySource` with higher precedence can override the list, you need to define it as a single property:`my: servers: dev.bar.com,foo.bar.com` |
+
+### 24.6.2 Exposing YAML as properties in the Spring Environment
+
+The `YamlPropertySourceLoader` class can be used to expose YAML as a `PropertySource` in the Spring `Environment`. This allows you to use the familiar `@Value` annotation with placeholders syntax to access YAML properties.
+
+### 24.6.3 Multi-profile YAML documents
+
+You can specify multiple profile-specific YAML documents in a single file by using a `spring.profiles` key to indicate when the document applies. For example:
+
+```
+server:
+ address: 192.168.1.100
+---
+spring:
+ profiles: development
+server:
+ address: 127.0.0.1
+---
+spring:
+ profiles: production
+server:
+ address: 192.168.1.120
+
+```
+
+In the example above, the `server.address` property will be `127.0.0.1` if the `development` profile is active. If the `development` and `production` profiles are **not** enabled, then the value for the property will be `192.168.1.100`.
+
+The default profiles are activated if none are explicitly active when the application context starts. So in this YAML we set a value for `security.user.password` that is**only** available in the "default" profile:
+
+```
+server:
+ port: 8000
+---
+spring:
+ profiles: default
+security:
+ user:
+ password: weak
+
+```
+
+whereas in this example, the password is always set because it isn’t attached to any profile, and it would have to be explicitly reset in all other profiles as necessary:
+
+```
+server:
+ port: 8000
+security:
+ user:
+ password: weak
+
+```
+
+Spring profiles designated using the "spring.profiles" element may optionally be negated using the `!` character. If both negated and non-negated profiles are specified for a single document, at least one non-negated profile must match and no negated profiles may match.
+
+### 24.6.4 YAML shortcomings
+
+YAML files can’t be loaded via the `@PropertySource` annotation. So in the case that you need to load values that way, you need to use a properties file.
+
+### 24.6.5 Merging YAML lists
+
+As [we have seen above](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-loading-yaml), any YAML content is ultimately transformed to properties. That process may be counter intuitive when overriding “list” properties via a profile.
+
+For example, assume a `MyPojo` object with `name` and `description` attributes that are `null` by default. Let’s expose a list of `MyPojo` from `FooProperties`:
+
+```
+@ConfigurationProperties("foo")
+public class FooProperties {
+
+ private final List list = new ArrayList<>();
+
+ public List getList() {
+ return this.list;
+ }
+
+}
+
+```
+
+Consider the following configuration:
+
+```
+foo:
+ list:
+ - name: my name
+ description: my description
+---
+spring:
+ profiles: dev
+foo:
+ list:
+ - name: my another name
+
+```
+
+If the `dev` profile isn’t active, `FooProperties.list` will contain one `MyPojo` entry as defined above. If the `dev` profile is enabled however, the `list` will *still* only contain one entry (with name “my another name” and description `null`). This configuration *will not* add a second `MyPojo` instance to the list, and it won’t merge the items.
+
+When a collection is specified in multiple profiles, the one with highest priority is used (and only that one):
+
+```
+foo:
+ list:
+ - name: my name
+ description: my description
+ - name: another name
+ description: another description
+---
+spring:
+ profiles: dev
+foo:
+ list:
+ - name: my another name
+
+```
+
+In the example above, considering that the `dev` profile is active, `FooProperties.list` will contain *one* `MyPojo` entry (with name “my another name” and description `null`).
+
+## 24.7 Type-safe Configuration Properties
+
+Using the `@Value("${property}")` annotation to inject configuration properties can sometimes be cumbersome, especially if you are working with multiple properties or your data is hierarchical in nature. Spring Boot provides an alternative method of working with properties that allows strongly typed beans to govern and validate the configuration of your application.
+
+```
+package com.example;
+
+import java.net.InetAddress;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+
+import org.springframework.boot.context.properties.ConfigurationProperties;
+
+@ConfigurationProperties("foo")
+public class FooProperties {
+
+ private boolean enabled;
+
+ private InetAddress remoteAddress;
+
+ private final Security security = new Security();
+
+ public boolean isEnabled() { ... }
+
+ public void setEnabled(boolean enabled) { ... }
+
+ public InetAddress getRemoteAddress() { ... }
+
+ public void setRemoteAddress(InetAddress remoteAddress) { ... }
+
+ public Security getSecurity() { ... }
+
+ public static class Security {
+
+ private String username;
+
+ private String password;
+
+ private List roles = new ArrayList<>(Collections.singleton("USER"));
+
+ public String getUsername() { ... }
+
+ public void setUsername(String username) { ... }
+
+ public String getPassword() { ... }
+
+ public void setPassword(String password) { ... }
+
+ public List getRoles() { ... }
+
+ public void setRoles(List roles) { ... }
+
+ }
+}
+
+```
+
+The POJO above defines the following properties:
+
+- `foo.enabled`, `false` by default
+- `foo.remote-address`, with a type that can be coerced from `String`
+- `foo.security.username`, with a nested "security" whose name is determined by the name of the property. In particular the return type is not used at all there and could have been `SecurityProperties`
+- `foo.security.password`
+- `foo.security.roles`, with a collection of `String`
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Getters and setters are usually mandatory, since binding is via standard Java Beans property descriptors, just like in Spring MVC. There are cases where a setter may be omitted:Maps, as long as they are initialized, need a getter but not necessarily a setter since they can be mutated by the binder.Collections and arrays can be either accessed via an index (typically with YAML) or using a single comma-separated value (properties). In the latter case, a setter is mandatory. We recommend to always add a setter for such types. If you initialize a collection, make sure it is not immutable (as in the example above)If nested POJO properties are initialized (like the `Security` field in the example above), a setter is not required. If you want the binder to create the instance on-the-fly using its default constructor, you will need a setter.Some people use Project Lombok to add getters and setters automatically. Make sure that Lombok doesn’t generate any particular constructor for such type as it will be used automatically by the container to instantiate the object. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| See also the [differences between `@Value` and `@ConfigurationProperties`](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-vs-value). |
+
+You also need to list the properties classes to register in the `@EnableConfigurationProperties` annotation:
+
+```
+@Configuration
+@EnableConfigurationProperties(FooProperties.class)
+public class MyConfiguration {
+}
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| When `@ConfigurationProperties` bean is registered that way, the bean will have a conventional name: `-`, where `` is the environment key prefix specified in the `@ConfigurationProperties` annotation and `` the fully qualified name of the bean. If the annotation does not provide any prefix, only the fully qualified name of the bean is used.The bean name in the example above will be `foo-com.example.FooProperties`. |
+
+Even if the configuration above will create a regular bean for `FooProperties`, we recommend that `@ConfigurationProperties` only deal with the environment and in particular does not inject other beans from the context. Having said that, The `@EnableConfigurationProperties` annotation is *also* automatically applied to your project so that any *existing* bean annotated with `@ConfigurationProperties` will be configured from the `Environment`. You could shortcut `MyConfiguration` above by making sure `FooProperties` is a already a bean:
+
+```
+@Component
+@ConfigurationProperties(prefix="foo")
+public class FooProperties {
+
+ // ... see above
+
+}
+
+```
+
+This style of configuration works particularly well with the `SpringApplication` external YAML configuration:
+
+```
+# application.yml
+
+foo:
+ remote-address: 192.168.1.1
+ security:
+ username: foo
+ roles:
+ - USER
+ - ADMIN
+
+# additional configuration as required
+
+```
+
+To work with `@ConfigurationProperties` beans you can just inject them in the same way as any other bean.
+
+```
+@Service
+public class MyService {
+
+ private final FooProperties properties;
+
+ @Autowired
+ public MyService(FooProperties properties) {
+ this.properties = properties;
+ }
+
+ //...
+
+ @PostConstruct
+ public void openConnection() {
+ Server server = new Server(this.properties.getRemoteAddress());
+ // ...
+ }
+
+}
+
+```
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Using `@ConfigurationProperties` also allows you to generate meta-data files that can be used by IDEs to offer auto-completion for your own keys, see the [Appendix B, *Configuration meta-data*](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata) appendix for details. |
+
+### 24.7.1 Third-party configuration
+
+As well as using `@ConfigurationProperties` to annotate a class, you can also use it on public `@Bean` methods. This can be particularly useful when you want to bind properties to third-party components that are outside of your control.
+
+To configure a bean from the `Environment` properties, add `@ConfigurationProperties` to its bean registration:
+
+```
+@ConfigurationProperties(prefix = "bar")
+@Bean
+public BarComponent barComponent() {
+ ...
+}
+
+```
+
+Any property defined with the `bar` prefix will be mapped onto that `BarComponent` bean in a similar manner as the `FooProperties` example above.
+
+### 24.7.2 Relaxed binding
+
+Spring Boot uses some relaxed rules for binding `Environment` properties to `@ConfigurationProperties` beans, so there doesn’t need to be an exact match between the `Environment` property name and the bean property name. Common examples where this is useful include dashed separated (e.g. `context-path`binds to `contextPath`), and capitalized (e.g. `PORT` binds to `port`) environment properties.
+
+For example, given the following `@ConfigurationProperties` class:
+
+```
+@ConfigurationProperties(prefix="person")
+public class OwnerProperties {
+
+ private String firstName;
+
+ public String getFirstName() {
+ return this.firstName;
+ }
+
+ public void setFirstName(String firstName) {
+ this.firstName = firstName;
+ }
+
+}
+
+```
+
+The following properties names can all be used:
+
+
+
+**Table 24.1. relaxed binding**
+
+| Property | Note |
+| ------------------- | ------------------------------------------------------------ |
+| `person.firstName` | Standard camel case syntax. |
+| `person.first-name` | Kebab-case, recommended for use in `.properties` and `.yml` files. |
+| `person.first_name` | Underscore notation, alternative format for use in `.properties` and `.yml` files. |
+| `PERSON_FIRSTNAME` | Upper case format. Recommended when using a system environment variables. |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| The `prefix` value for the annotation must be in kebab-case, ie, lowercase and separated by `-`. |
+
+
+
+**Table 24.2. relaxed binding rules per property source**
+
+| Property Source | Simple | List |
+| --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| Properties Files | Camel-case, kebab-case or underscore notation | Standard list syntax using `[ ]` or comma-separated values |
+| YAML Files | Camel-case, kebab-case or underscore notation | Standard YAML list syntax or comma-separated values |
+| Environment Variables | Upper case format with underscore as the delimiter. `_` should not be used within a property name | Numeric values surrounded by underscores. eg: `MY_FOO_1_BAR = my.foo[1].bar` |
+| System properties | Camel-case, kebab-case or underscore notation | Standard list syntax using `[ ]` or comma-separated values |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| We recommend that, when possible, properties are stored in lowercase kebab format. i.e. `my.property-name=foo` |
+
+### 24.7.3 Properties conversion
+
+Spring will attempt to coerce the external application properties to the right type when it binds to the `@ConfigurationProperties` beans. If you need custom type conversion you can provide a `ConversionService` bean (with bean id `conversionService`) or custom property editors (via a `CustomEditorConfigurer`bean) or custom `Converters` (with bean definitions annotated as `@ConfigurationPropertiesBinding`).
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| As this bean is requested very early during the application lifecycle, make sure to limit the dependencies that your `ConversionService` is using. Typically, any dependency that you require may not be fully initialized at creation time. You may want to rename your custom `ConversionService` if it’s not required for configuration keys coercion and only rely on custom converters qualified with `@ConfigurationPropertiesBinding`. |
+
+### 24.7.4 @ConfigurationProperties Validation
+
+Spring Boot will attempt to validate `@ConfigurationProperties` classes whenever they are annotated with Spring’s `@Validated` annotation. You can use JSR-303 `javax.validation` constraint annotations directly on your configuration class. Simply ensure that a compliant JSR-303 implementation is on your classpath, then add constraint annotations to your fields:
+
+```
+@ConfigurationProperties(prefix="foo")
+@Validated
+public class FooProperties {
+
+ @NotNull
+ private InetAddress remoteAddress;
+
+ // ... getters and setters
+
+}
+
+```
+
+In order to validate values of nested properties, you must annotate the associated field as `@Valid` to trigger its validation. For example, building upon the above`FooProperties` example:
+
+```
+@ConfigurationProperties(prefix="connection")
+@Validated
+public class FooProperties {
+
+ @NotNull
+ private InetAddress remoteAddress;
+
+ @Valid
+ private final Security security = new Security();
+
+ // ... getters and setters
+
+ public static class Security {
+
+ @NotEmpty
+ public String username;
+
+ // ... getters and setters
+
+ }
+
+}
+
+```
+
+You can also add a custom Spring `Validator` by creating a bean definition called `configurationPropertiesValidator`. The `@Bean` method should be declared `static`. The configuration properties validator is created very early in the application’s lifecycle and declaring the `@Bean` method as static allows the bean to be created without having to instantiate the `@Configuration` class. This avoids any problems that may be caused by early instantiation. There is a [property validation sample](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-samples/spring-boot-sample-property-validation) so you can see how to set things up.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The `spring-boot-actuator` module includes an endpoint that exposes all `@ConfigurationProperties` beans. Simply point your web browser to `/configprops` or use the equivalent JMX endpoint. See the *Production ready features*. section for details. |
+
+### 24.7.5 @ConfigurationProperties vs. @Value
+
+`@Value` is a core container feature and it does not provide the same features as type-safe Configuration Properties. The table below summarizes the features that are supported by `@ConfigurationProperties` and `@Value`:
+
+| Feature | `@ConfigurationProperties` | `@Value` |
+| ------------------------------------------------------------ | -------------------------- | -------- |
+| [Relaxed binding](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-relaxed-binding) | Yes | No |
+| [Meta-data support](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#configuration-metadata) | Yes | No |
+| `SpEL` evaluation | No | Yes |
+
+If you define a set of configuration keys for your own components, we recommend you to group them in a POJO annotated with `@ConfigurationProperties`. Please also be aware that since `@Value` does not support relaxed binding, it isn’t a great candidate if you need to provide the value using environment variables.
+
+Finally, while you can write a `SpEL` expression in `@Value`, such expressions are not processed from [Application property files](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-application-property-files).
+
+## 25. Profiles
+
+Spring Profiles provide a way to segregate parts of your application configuration and make it only available in certain environments. Any `@Component` or `@Configuration` can be marked with `@Profile` to limit when it is loaded:
+
+```
+@Configuration
+@Profile("production")
+public class ProductionConfiguration {
+
+ // ...
+
+}
+
+```
+
+In the normal Spring way, you can use a `spring.profiles.active` `Environment` property to specify which profiles are active. You can specify the property in any of the usual ways, for example you could include it in your `application.properties`:
+
+```
+spring.profiles.active=dev,hsqldb
+
+```
+
+or specify on the command line using the switch `--spring.profiles.active=dev,hsqldb`.
+
+## 25.1 Adding active profiles
+
+The `spring.profiles.active` property follows the same ordering rules as other properties, the highest `PropertySource` will win. This means that you can specify active profiles in `application.properties` then **replace** them using the command line switch.
+
+Sometimes it is useful to have profile-specific properties that **add** to the active profiles rather than replace them. The `spring.profiles.include` property can be used to unconditionally add active profiles. The `SpringApplication` entry point also has a Java API for setting additional profiles (i.e. on top of those activated by the`spring.profiles.active` property): see the `setAdditionalProfiles()` method.
+
+For example, when an application with following properties is run using the switch `--spring.profiles.active=prod` the `proddb` and `prodmq` profiles will also be activated:
+
+```
+---
+my.property: fromyamlfile
+---
+spring.profiles: prod
+spring.profiles.include:
+ - proddb
+ - prodmq
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Remember that the `spring.profiles` property can be defined in a YAML document to determine when this particular document is included in the configuration. See [Section 73.7, “Change configuration depending on the environment”](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#howto-change-configuration-depending-on-the-environment) for more details. |
+
+## 25.2 Programmatically setting profiles
+
+You can programmatically set active profiles by calling `SpringApplication.setAdditionalProfiles(…)` before your application runs. It is also possible to activate profiles using Spring’s `ConfigurableEnvironment` interface.
+
+## 25.3 Profile-specific configuration files
+
+Profile-specific variants of both `application.properties` (or `application.yml`) and files referenced via `@ConfigurationProperties` are considered as files are loaded. See *Section 24.4, “Profile-specific properties”* for details.
+
+## 26. Logging
+
+Spring Boot uses [Commons Logging](https://commons.apache.org/logging) for all internal logging, but leaves the underlying log implementation open. Default configurations are provided for [Java Util Logging](https://docs.oracle.com/javase/7/docs/api/java/util/logging/package-summary.html),[Log4J2](https://logging.apache.org/log4j/2.x/) and [Logback](http://logback.qos.ch/). In each case loggers are pre-configured to use console output with optional file output also available.
+
+By default, If you use the ‘Starters’, Logback will be used for logging. Appropriate Logback routing is also included to ensure that dependent libraries that use Java Util Logging, Commons Logging, Log4J or SLF4J will all work correctly.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| There are a lot of logging frameworks available for Java. Don’t worry if the above list seems confusing. Generally you won’t need to change your logging dependencies and the Spring Boot defaults will work just fine. |
+
+## 26.1 Log format
+
+The default log output from Spring Boot looks like this:
+
+```
+2014-03-05 10:57:51.112 INFO 45469 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache Tomcat/7.0.52
+2014-03-05 10:57:51.253 INFO 45469 --- [ost-startStop-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
+2014-03-05 10:57:51.253 INFO 45469 --- [ost-startStop-1] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 1358 ms
+2014-03-05 10:57:51.698 INFO 45469 --- [ost-startStop-1] o.s.b.c.e.ServletRegistrationBean : Mapping servlet: 'dispatcherServlet' to [/]
+2014-03-05 10:57:51.702 INFO 45469 --- [ost-startStop-1] o.s.b.c.embedded.FilterRegistrationBean : Mapping filter: 'hiddenHttpMethodFilter' to: [/*]
+
+```
+
+The following items are output:
+
+- Date and Time — Millisecond precision and easily sortable.
+- Log Level — `ERROR`, `WARN`, `INFO`, `DEBUG` or `TRACE`.
+- Process ID.
+- A `---` separator to distinguish the start of actual log messages.
+- Thread name — Enclosed in square brackets (may be truncated for console output).
+- Logger name — This is usually the source class name (often abbreviated).
+- The log message.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Logback does not have a `FATAL` level (it is mapped to `ERROR`) |
+
+## 26.2 Console output
+
+The default log configuration will echo messages to the console as they are written. By default `ERROR`, `WARN` and `INFO` level messages are logged. You can also enable a “debug” mode by starting your application with a `--debug` flag.
+
+```
+$ java -jar myapp.jar --debug
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| you can also specify `debug=true` in your `application.properties`. |
+
+When the debug mode is enabled, a selection of core loggers (embedded container, Hibernate and Spring Boot) are configured to output more information. Enabling the debug mode does *not* configure your application to log all messages with `DEBUG` level.
+
+Alternatively, you can enable a “trace” mode by starting your application with a `--trace` flag (or `trace=true` in your `application.properties`). This will enable trace logging for a selection of core loggers (embedded container, Hibernate schema generation and the whole Spring portfolio).
+
+### 26.2.1 Color-coded output
+
+If your terminal supports ANSI, color output will be used to aid readability. You can set `spring.output.ansi.enabled` to a [supported value](https://docs.spring.io/spring-boot/docs/2.0.0.M3/api/org/springframework/boot/ansi/AnsiOutput.Enabled.html) to override the auto detection.
+
+Color coding is configured using the `%clr` conversion word. In its simplest form the converter will color the output according to the log level, for example:
+
+```
+%clr(%5p)
+
+```
+
+The mapping of log level to a color is as follows:
+
+| Level | Color |
+| ------- | ------ |
+| `FATAL` | Red |
+| `ERROR` | Red |
+| `WARN` | Yellow |
+| `INFO` | Green |
+| `DEBUG` | Green |
+| `TRACE` | Green |
+
+Alternatively, you can specify the color or style that should be used by providing it as an option to the conversion. For example, to make the text yellow:
+
+```
+%clr(%d{yyyy-MM-dd HH:mm:ss.SSS}){yellow}
+
+```
+
+The following colors and styles are supported:
+
+- `blue`
+- `cyan`
+- `faint`
+- `green`
+- `magenta`
+- `red`
+- `yellow`
+
+## 26.3 File output
+
+By default, Spring Boot will only log to the console and will not write log files. If you want to write log files in addition to the console output you need to set a`logging.file` or `logging.path` property (for example in your `application.properties`).
+
+The following table shows how the `logging.*` properties can be used together:
+
+
+
+**Table 26.1. Logging properties**
+
+| `logging.file` | `logging.path` | Example | Description |
+| -------------- | ------------------ | ---------- | ------------------------------------------------------------ |
+| *(none)* | *(none)* | | Console only logging. |
+| Specific file | *(none)* | `my.log` | Writes to the specified log file. Names can be an exact location or relative to the current directory. |
+| *(none)* | Specific directory | `/var/log` | Writes `spring.log` to the specified directory. Names can be an exact location or relative to the current directory. |
+
+Log files will rotate when they reach 10 MB and as with console output, `ERROR`, `WARN` and `INFO` level messages are logged by default.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| The logging system is initialized early in the application lifecycle and as such logging properties will not be found in property files loaded via `@PropertySource` annotations. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Logging properties are independent of the actual logging infrastructure. As a result, specific configuration keys (such as `logback.configurationFile`for Logback) are not managed by spring Boot. |
+
+## 26.4 Log Levels
+
+All the supported logging systems can have the logger levels set in the Spring `Environment` (so for example in `application.properties`) using ‘logging.level.*=LEVEL’ where ‘LEVEL’ is one of TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. The `root` logger can be configured using `logging.level.root`. Example `application.properties`:
+
+```
+logging.level.root=WARN
+logging.level.org.springframework.web=DEBUG
+logging.level.org.hibernate=ERROR
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| By default Spring Boot remaps Thymeleaf `INFO` messages so that they are logged at `DEBUG` level. This helps to reduce noise in the standard log output. See [`LevelRemappingAppender`](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot/src/main/java/org/springframework/boot/logging/logback/LevelRemappingAppender.java) for details of how you can apply remapping in your own configuration. |
+
+## 26.5 Custom log configuration
+
+The various logging systems can be activated by including the appropriate libraries on the classpath, and further customized by providing a suitable configuration file in the root of the classpath, or in a location specified by the Spring `Environment` property `logging.config`.
+
+You can force Spring Boot to use a particular logging system using the `org.springframework.boot.logging.LoggingSystem` system property. The value should be the fully-qualified class name of a `LoggingSystem` implementation. You can also disable Spring Boot’s logging configuration entirely by using a value of `none`.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Since logging is initialized **before** the `ApplicationContext` is created, it isn’t possible to control logging from `@PropertySources` in Spring `@Configuration` files. System properties and the conventional Spring Boot external configuration files work just fine.) |
+
+Depending on your logging system, the following files will be loaded:
+
+| Logging System | Customization |
+| ----------------------- | ------------------------------------------------------------ |
+| Logback | `logback-spring.xml`, `logback-spring.groovy`, `logback.xml` or `logback.groovy` |
+| Log4j2 | `log4j2-spring.xml` or `log4j2.xml` |
+| JDK (Java Util Logging) | `logging.properties` |
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| When possible we recommend that you use the `-spring` variants for your logging configuration (for example `logback-spring.xml` rather than `logback.xml`). If you use standard configuration locations, Spring cannot completely control log initialization. |
+
+| ![[Warning]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/warning.png) |
+| ------------------------------------------------------------ |
+| There are known classloading issues with Java Util Logging that cause problems when running from an ‘executable jar’. We recommend that you avoid it if at all possible. |
+
+To help with the customization some other properties are transferred from the Spring `Environment` to System properties:
+
+| Spring Environment | System Property | Comments |
+| ----------------------------------- | ------------------------------- | ------------------------------------------------------------ |
+| `logging.exception-conversion-word` | `LOG_EXCEPTION_CONVERSION_WORD` | The conversion word that’s used when logging exceptions. |
+| `logging.file` | `LOG_FILE` | Used in default log configuration if defined. |
+| `logging.path` | `LOG_PATH` | Used in default log configuration if defined. |
+| `logging.pattern.console` | `CONSOLE_LOG_PATTERN` | The log pattern to use on the console (stdout). (Only supported with the default logback setup.) |
+| `logging.pattern.file` | `FILE_LOG_PATTERN` | The log pattern to use in a file (if LOG_FILE enabled). (Only supported with the default logback setup.) |
+| `logging.pattern.level` | `LOG_LEVEL_PATTERN` | The format to use to render the log level (default `%5p`). (Only supported with the default logback setup.) |
+| `PID` | `PID` | The current process ID (discovered if possible and when not already defined as an OS environment variable). |
+
+All the logging systems supported can consult System properties when parsing their configuration files. See the default configurations in `spring-boot.jar` for examples.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| If you want to use a placeholder in a logging property, you should use [Spring Boot’s syntax](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-external-config-placeholders-in-properties) and not the syntax of the underlying framework. Notably, if you’re using Logback, you should use `:` as the delimiter between a property name and its default value and not `:-`. |
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| You can add MDC and other ad-hoc content to log lines by overriding only the `LOG_LEVEL_PATTERN` (or `logging.pattern.level` with Logback). For example, if you use `logging.pattern.level=user:%X{user} %5p` then the default log format will contain an MDC entry for "user" if it exists, e.g.`2015-09-30 12:30:04.031 user:juergen INFO 22174 --- [ nio-8080-exec-0] demo.Controller Handling authenticated request` |
+
+## 26.6 Logback extensions
+
+Spring Boot includes a number of extensions to Logback which can help with advanced configuration. You can use these extensions in your `logback-spring.xml`configuration file.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| You cannot use extensions in the standard `logback.xml` configuration file since it’s loaded too early. You need to either use `logback-spring.xml` or define a `logging.config` property. |
+
+| ![[Warning]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/warning.png) |
+| ------------------------------------------------------------ |
+| The extensions cannot be used with Logback’s [configuration scanning](http://logback.qos.ch/manual/configuration.html#autoScan). If you attempt to do so, making changes to the configuration file will result in an error similar to one of the following being logged: |
+
+```
+ERROR in ch.qos.logback.core.joran.spi.Interpreter@4:71 - no applicable action for [springProperty], current ElementPath is [[configuration][springProperty]]
+ERROR in ch.qos.logback.core.joran.spi.Interpreter@4:71 - no applicable action for [springProfile], current ElementPath is [[configuration][springProfile]]
+
+```
+
+### 26.6.1 Profile-specific configuration
+
+The `` tag allows you to optionally include or exclude sections of configuration based on the active Spring profiles. Profile sections are supported anywhere within the `` element. Use the `name` attribute to specify which profile accepts the configuration. Multiple profiles can be specified using a comma-separated list.
+
+```
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### 26.6.2 Environment properties
+
+The `` tag allows you to surface properties from the Spring `Environment` for use within Logback. This can be useful if you want to access values from your `application.properties` file in your logback configuration. The tag works in a similar way to Logback’s standard `` tag, but rather than specifying a direct `value` you specify the `source` of the property (from the `Environment`). You can use the `scope` attribute if you need to store the property somewhere other than in `local` scope. If you need a fallback value in case the property is not set in the `Environment`, you can use the `defaultValue` attribute.
+
+```
+
+
+ ${fluentHost}
+ ...
+
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| The `source` must be specified using kebab-case (`my.property-name`). However, properties can be added to the `Environment` using the relaxed rules. |
+
+## 27. Developing web applications
+
+Spring Boot is well suited for web application development. You can easily create a self-contained HTTP server using embedded Tomcat, Jetty, Undertow, or Netty. Most web applications will use the `spring-boot-starter-web` module to get up and running quickly. You can also choose to use to build reactive web applications by using the `spring-boot-starter-webflux` module.
+
+If you haven’t yet developed a Spring Boot web application you can follow the "Hello World!" example in the *Getting started* section.
+
+## 27.1 The ‘Spring Web MVC framework’
+
+The Spring Web MVC framework (often referred to as simply ‘Spring MVC’) is a rich ‘model view controller’ web framework. Spring MVC lets you create special `@Controller` or `@RestController` beans to handle incoming HTTP requests. Methods in your controller are mapped to HTTP using `@RequestMapping`annotations.
+
+Here is a typical example `@RestController` to serve JSON data:
+
+```
+@RestController
+@RequestMapping(value="/users")
+public class MyRestController {
+
+ @RequestMapping(value="/{user}", method=RequestMethod.GET)
+ public User getUser(@PathVariable Long user) {
+ // ...
+ }
+
+ @RequestMapping(value="/{user}/customers", method=RequestMethod.GET)
+ List getUserCustomers(@PathVariable Long user) {
+ // ...
+ }
+
+ @RequestMapping(value="/{user}", method=RequestMethod.DELETE)
+ public User deleteUser(@PathVariable Long user) {
+ // ...
+ }
+
+}
+
+```
+
+Spring MVC is part of the core Spring Framework and detailed information is available in the [reference documentation](https://docs.spring.io/spring/docs/5.0.0.RC3/spring-framework-reference/web.html#mvc). There are also several guides available at [spring.io/guides](https://spring.io/guides) that cover Spring MVC.
+
+### 27.1.1 Spring MVC auto-configuration
+
+Spring Boot provides auto-configuration for Spring MVC that works well with most applications.
+
+The auto-configuration adds the following features on top of Spring’s defaults:
+
+- Inclusion of `ContentNegotiatingViewResolver` and `BeanNameViewResolver` beans.
+- Support for serving static resources, including support for WebJars (see below).
+- Automatic registration of `Converter`, `GenericConverter`, `Formatter` beans.
+- Support for `HttpMessageConverters` (see below).
+- Automatic registration of `MessageCodesResolver` (see below).
+- Static `index.html` support.
+- Custom `Favicon` support (see below).
+- Automatic use of a `ConfigurableWebBindingInitializer` bean (see below).
+
+If you want to keep Spring Boot MVC features, and you just want to add additional [MVC configuration](https://docs.spring.io/spring/docs/5.0.0.RC3/spring-framework-reference/web.html#mvc) (interceptors, formatters, view controllers etc.) you can add your own `@Configuration` class of type `WebMvcConfigurer`, but **without** `@EnableWebMvc`. If you wish to provide custom instances of `RequestMappingHandlerMapping`, `RequestMappingHandlerAdapter` or `ExceptionHandlerExceptionResolver` you can declare a `WebMvcRegistrationsAdapter` instance providing such components.
+
+If you want to take complete control of Spring MVC, you can add your own `@Configuration` annotated with `@EnableWebMvc`.
+
+### 27.1.2 HttpMessageConverters
+
+Spring MVC uses the `HttpMessageConverter` interface to convert HTTP requests and responses. Sensible defaults are included out of the box, for example Objects can be automatically converted to JSON (using the Jackson library) or XML (using the Jackson XML extension if available, else using JAXB). Strings are encoded using `UTF-8` by default.
+
+If you need to add or customize converters you can use Spring Boot’s `HttpMessageConverters` class:
+
+```
+import org.springframework.boot.autoconfigure.web.HttpMessageConverters;
+import org.springframework.context.annotation.*;
+import org.springframework.http.converter.*;
+
+@Configuration
+public class MyConfiguration {
+
+ @Bean
+ public HttpMessageConverters customConverters() {
+ HttpMessageConverter> additional = ...
+ HttpMessageConverter> another = ...
+ return new HttpMessageConverters(additional, another);
+ }
+
+}
+
+```
+
+Any `HttpMessageConverter` bean that is present in the context will be added to the list of converters. You can also override default converters that way.
+
+### 27.1.3 Custom JSON Serializers and Deserializers
+
+If you’re using Jackson to serialize and deserialize JSON data, you might want to write your own `JsonSerializer` and `JsonDeserializer` classes. Custom serializers are usually [registered with Jackson via a Module](http://wiki.fasterxml.com/JacksonHowToCustomDeserializers), but Spring Boot provides an alternative `@JsonComponent` annotation which makes it easier to directly register Spring Beans.
+
+You can use `@JsonComponent` directly on `JsonSerializer` or `JsonDeserializer` implementations. You can also use it on classes that contains serializers/deserializers as inner-classes. For example:
+
+```
+import java.io.*;
+import com.fasterxml.jackson.core.*;
+import com.fasterxml.jackson.databind.*;
+import org.springframework.boot.jackson.*;
+
+@JsonComponent
+public class Example {
+
+ public static class Serializer extends JsonSerializer {
+ // ...
+ }
+
+ public static class Deserializer extends JsonDeserializer {
+ // ...
+ }
+
+}
+
+```
+
+All `@JsonComponent` beans in the `ApplicationContext` will be automatically registered with Jackson, and since `@JsonComponent` is meta-annotated with `@Component`, the usual component-scanning rules apply.
+
+Spring Boot also provides [`JsonObjectSerializer`](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot/src/main/java/org/springframework/boot/jackson/JsonObjectSerializer.java) and [`JsonObjectDeserializer`](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot/src/main/java/org/springframework/boot/jackson/JsonObjectDeserializer.java) base classes which provide useful alternatives to the standard Jackson versions when serializing Objects. See the Javadoc for details.
+
+### 27.1.4 MessageCodesResolver
+
+Spring MVC has a strategy for generating error codes for rendering error messages from binding errors: `MessageCodesResolver`. Spring Boot will create one for you if you set the `spring.mvc.message-codes-resolver.format` property `PREFIX_ERROR_CODE` or `POSTFIX_ERROR_CODE` (see the enumeration in `DefaultMessageCodesResolver.Format`).
+
+### 27.1.5 Static Content
+
+By default Spring Boot will serve static content from a directory called `/static` (or `/public` or `/resources` or `/META-INF/resources`) in the classpath or from the root of the `ServletContext`. It uses the `ResourceHttpRequestHandler` from Spring MVC so you can modify that behavior by adding your own `WebMvcConfigurer` and overriding the `addResourceHandlers` method.
+
+In a stand-alone web application the default servlet from the container is also enabled, and acts as a fallback, serving content from the root of the `ServletContext` if Spring decides not to handle it. Most of the time this will not happen (unless you modify the default MVC configuration) because Spring will always be able to handle requests through the `DispatcherServlet`.
+
+By default, resources are mapped on `/**` but you can tune that via `spring.mvc.static-path-pattern`. For instance, relocating all resources to `/resources/**` can be achieved as follows:
+
+```
+spring.mvc.static-path-pattern=/resources/**
+
+```
+
+You can also customize the static resource locations using `spring.resources.static-locations` (replacing the default values with a list of directory locations). If you do this the default welcome page detection will switch to your custom locations, so if there is an `index.html` in any of your locations on startup, it will be the home page of the application.
+
+In addition to the ‘standard’ static resource locations above, a special case is made for [Webjars content](http://www.webjars.org/). Any resources with a path in `/webjars/**` will be served from jar files if they are packaged in the Webjars format.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| Do not use the `src/main/webapp` directory if your application will be packaged as a jar. Although this directory is a common standard, it will **only** work with war packaging and it will be silently ignored by most build tools if you generate a jar. |
+
+Spring Boot also supports advanced resource handling features provided by Spring MVC, allowing use cases such as cache busting static resources or using version agnostic URLs for Webjars.
+
+To use version agnostic URLs for Webjars, simply add the `webjars-locator` dependency. Then declare your Webjar, taking jQuery for example, as `"/webjars/jquery/dist/jquery.min.js"` which results in `"/webjars/jquery/x.y.z/dist/jquery.min.js"` where `x.y.z` is the Webjar version.
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| If you are using JBoss, you’ll need to declare the `webjars-locator-jboss-vfs` dependency instead of the `webjars-locator`; otherwise all Webjars resolve as a `404`. |
+
+To use cache busting, the following configuration will configure a cache busting solution for all static resources, effectively adding a content hash in URLs, such as``:
+
+```
+spring.resources.chain.strategy.content.enabled=true
+spring.resources.chain.strategy.content.paths=/**
+
+```
+
+| ![[Note]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/note.png) |
+| ------------------------------------------------------------ |
+| Links to resources are rewritten at runtime in template, thanks to a `ResourceUrlEncodingFilter`, auto-configured for Thymeleaf and FreeMarker. You should manually declare this filter when using JSPs. Other template engines aren’t automatically supported right now, but can be with custom template macros/helpers and the use of the [`ResourceUrlProvider`](https://docs.spring.io/spring/docs/5.0.0.RC3/javadoc-api/org/springframework/web/servlet/resource/ResourceUrlProvider.html). |
+
+When loading resources dynamically with, for example, a JavaScript module loader, renaming files is not an option. That’s why other strategies are also supported and can be combined. A "fixed" strategy will add a static version string in the URL, without changing the file name:
+
+```
+spring.resources.chain.strategy.content.enabled=true
+spring.resources.chain.strategy.content.paths=/**
+spring.resources.chain.strategy.fixed.enabled=true
+spring.resources.chain.strategy.fixed.paths=/js/lib/
+spring.resources.chain.strategy.fixed.version=v12
+
+```
+
+With this configuration, JavaScript modules located under `"/js/lib/"` will use a fixed versioning strategy `"/v12/js/lib/mymodule.js"` while other resources will still use the content one ``.
+
+See [`ResourceProperties`](https://github.com/spring-projects/spring-boot/tree/v2.0.0.M3/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/web/ResourceProperties.java) for more of the supported options.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| This feature has been thoroughly described in a dedicated [blog post](https://spring.io/blog/2014/07/24/spring-framework-4-1-handling-static-web-resources) and in Spring Framework’s [reference documentation](https://docs.spring.io/spring/docs/5.0.0.RC3/spring-framework-reference/web.html#mvc-config-static-resources). |
+
+### 27.1.6 Custom Favicon
+
+Spring Boot looks for a `favicon.ico` in the configured static content locations and the root of the classpath (in that order). If such file is present, it is automatically used as the favicon of the application.
+
+### 27.1.7 ConfigurableWebBindingInitializer
+
+Spring MVC uses a `WebBindingInitializer` to initialize a `WebDataBinder` for a particular request. If you create your own `ConfigurableWebBindingInitializer` `@Bean`, Spring Boot will automatically configure Spring MVC to use it.
+
+### 27.1.8 Template engines
+
+As well as REST web services, you can also use Spring MVC to serve dynamic HTML content. Spring MVC supports a variety of templating technologies including Thymeleaf, FreeMarker and JSPs. Many other templating engines also ship their own Spring MVC integrations.
+
+Spring Boot includes auto-configuration support for the following templating engines:
+
+- [FreeMarker](http://freemarker.org/docs/)
+- [Groovy](http://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html#_the_markuptemplateengine)
+- [Thymeleaf](http://www.thymeleaf.org/)
+- [Mustache](https://mustache.github.io/)
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| JSPs should be avoided if possible, there are several [known limitations](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/#boot-features-jsp-limitations) when using them with embedded servlet containers. |
+
+When you’re using one of these templating engines with the default configuration, your templates will be picked up automatically from `src/main/resources/templates`.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| IntelliJ IDEA orders the classpath differently depending on how you run your application. Running your application in the IDE via its main method will result in a different ordering to when you run your application using Maven or Gradle or from its packaged jar. This can cause Spring Boot to fail to find the templates on the classpath. If you’re affected by this problem you can reorder the classpath in the IDE to place the module’s classes and resources first. Alternatively, you can configure the template prefix to search every templates directory on the classpath: `classpath*:/templates/`. |
+
+### 27.1.9 Error Handling
+
+Spring Boot provides an `/error` mapping by default that handles all errors in a sensible way, and it is registered as a ‘global’ error page in the servlet container. For machine clients it will produce a JSON response with details of the error, the HTTP status and the exception message. For browser clients there is a ‘whitelabel’ error view that renders the same data in HTML format (to customize it just add a `View` that resolves to ‘error’). To replace the default behaviour completely you can implement`ErrorController` and register a bean definition of that type, or simply add a bean of type `ErrorAttributes` to use the existing mechanism but replace the contents.
+
+| ![[Tip]](https://docs.spring.io/spring-boot/docs/2.0.0.M3/reference/htmlsingle/images/tip.png) |
+| ------------------------------------------------------------ |
+| The `BasicErrorController` can be used as a base class for a custom `ErrorController`. This is particularly useful if you want to add a handler for a new content type (the default is to handle `text/html` specifically and provide a fallback for everything else). To do that just extend `BasicErrorController` and add a public method with a `@RequestMapping` that has a `produces` attribute, and create a bean of your new type. |
+
+You can also define a `@ControllerAdvice` to customize the JSON document to return for a particular controller and/or exception type.
+
+```
+@ControllerAdvice(basePackageClasses = FooController.class)
+public class FooControllerAdvice extends ResponseEntityExceptionHandler {
+
+ @ExceptionHandler(YourException.class)
+ @ResponseBody
+ ResponseEntity> handleControllerException(HttpServletRequest request, Throwable ex) {
+ HttpStatus status = getStatus(request);
+ return new ResponseEntity<>(new CustomErrorType(status.value(), ex.getMessage()), status);
+ }
+
+ private HttpStatus getStatus(HttpServletRequest request) {
+ Integer statusCode = (Integer) request.getAttribute("javax.servlet.error.status_code");
+ if (statusCode == null) {
+ return HttpStatus.INTERNAL_SERVER_ERROR;
+ }
+ return HttpStatus.valueOf(statusCode);
+ }
+
+}
+
+```
+
+In the example above, if `YourException` is thrown by a controller defined in the same package as `FooController`, a json representation of the `CustomerErrorType` POJO will be used instead of the `ErrorAttributes` representation.
+
+#### Custom error pages
+
+If you want to display a custom HTML error page for a given status code, you add a file to an `/error` folder. Error pages can either be static HTML (i.e. added under any of the static resource folders) or built using templates. The name of the file should be the exact status code or a series mask.
+
+For example, to map `404` to a static HTML file, your folder structure would look like this:
+
+```
+src/
+ +- main/
+ +- java/
+ | +