I have had a lot of fun watching the Spring Boot project grow into an amazing product over the last few years. A month ago I looked at the Spring 2.0 Roadmap and today we get to start walking down that road.
It is so exciting to see all of the new features coming in both Spring Framework 5 and Spring Boot 2.0. In this article, we are going to look at the first milestone release of Spring Boot 2.0. We will talk about how to update your current projects, start a new one and a brief look at the new features.
Getting Started with Spring 2.0
The first thing you need to do to get started with Spring 2.0 is to update the version number to 2.0.0.M1.
<relativePath/> <!-- lookup parent from repository -->
If you’re creating a new project in IntelliJ just change the version number on the dependencies screen to 2.0.0.M1.
If you are upgrading from 1.5 there are a few things that you should know.
Java 8 baseline
Spring Boot 2.0 requires Java 8 or later. Java 6 and 7 are no longer supported.
@ConditionalOnBean now uses a logical AND rather than a logical OR when determining whether or not the condition has been met.
Following its depreciation in 1.5, support for the CRaSH project and remote actuator SSH support that it provided has been removed.
As the Spring Loaded project has been moved to the attic, its support has been removed. We advise using Devtools instead.
It is no longer possible to auto-configure both a general
HazelcastInstance and a dedicated
HazelcastInstance for caching. As a result, the
spring.cache.hazelcast.configproperty is no longer available.
The default connection pool has switched from Tomcat to HikariCP. If you used
spring.datasource.type to force the use of Hikari in a Tomcat-based application, you can now remove that override.
The default dispatcher types for a Filter are now
DipatcherType.REQUEST this aligns Spring Boot’s default with the Servlet specification’s default.
Spring Security’s filter is now auto-configured with
REQUEST dispatcher types. This aligns Spring Boot’s default configuration with Spring Security’s default configuration.
Spring Session’s filter is now auto-configured with
REQUEST dispatcher types. This aligns Spring Boot’s default configuration with Spring Session’s default configuration. Note that as of Spring Session 2.0, Mongo and GemFire support has been removed.
The minimum supported version of SendGrid’s Java client is now 3.2. In support of this upgrade, the
password properties have been removed as an API key is now the only supported means of authentication.
Previously several Spring Boot starters were transitively depending on Spring MVC with
spring-boot-starter-web. With the new support of Spring WebFlux,
spring-boot-starter-thymeleaf aren’t depending on on those anymore. It is the developer’s responsibility to choose and add
spring-boot-starter-webflux as dependencies.
The detail of the health check for Solr no longer defines a
solrStatus attribute. Rather a
status property is now defined and corresponds to the integer value of the standard
Spring Boot now uses CGLIB proxying by default, including for the AOP support. If you need proxy-based proxy, you’ll need to set the
Testing support has been removed from Spring Boot’s CLI in favour of moving to building the application with Maven or Gradle and using their rich testing support.
To better reflect their Servlet-specific nature, the multipart
spring.http.multipart.configuration properties have been renamed to
Spring 2.0 New Features
Spring Framework 5.0
Spring Boot 2.0 builds on and requires Spring Framework 5.0. There are a number of nice refinements in Spring Framework 5.0 including extensive support for building reactive applications. Please refer to the Spring Framework Wiki for details.
Spring Boot 2.0 provides a new starter for supporting the Reactive Spring web frameworks, for both annotation and functional based variants.
spring-boot-starter-webflux brings WebFlux itself, plus Reactor Netty as a default web engine (
Spring Boot 2.0 provides auto-configuration for the following data store with reactive support:
- MongoDB (
- Redis (
- Cassandra (
@DataMongoTest also enables reactive repositories if necessary.
Reactive controllers can be tested using
@WebFluxTest that provides a similar support than
@WebMvcTest for Spring MVC. In particular a
WebTestClient is auto-configured.
@SpringBootTest with an actual server (that is, either
WebTestClient is available the same way
bootRepackage task has been replaced with
bootWar tasks for building executable jars and wars respectively. Both tasks extend their equivalent standard Gradle jar or war task, giving you access to all of the usual configuration options and behaviour.
Spring Boot’s Gradle plugin no longer automatically applies the dependency management plugin. Instead, Spring Boot’s plugin now reacts to the dependency management plugin being applied by importing the correct version of the
spring-boot-dependencies bom. This gives you more control over how and when dependency management is configured. For most applications applying the dependency management plugin will be sufficient:
apply <span class="pl-c1">plugin</span>: <span class="pl-s"><span class="pl-pds">'</span>io.spring.dependency-management<span class="pl-pds">'</span></span>
Please note that the dependency management plugin remains a transitive dependency of
spring-boot-gradle-plugin so there’s no need for it to be listed as a
classpathdependency in your
SPRING 2.0 COURSE
If you haven’t already had a chance to check out my Spring Boot Introduction course please do. This course is based on Spring Boot 1.3 and was very much an introduction. My announcement today is that a Spring 2.0 course is coming and I will be releasing it sometime around SpringOne.
This is not just going to be a repeat of the previous course with a few new features. First off, I am going to create 2 free courses for setting up your development environment on both Windows 10 and Mac OS. Next, I will incorporate the feedback I have received from my current students. My current course is the best selling course on one platform and I know there is tons of room for improvement.
These courses will allow me to extract that portion of the course that some find necessary and others find boring. These courses will be bundled for free into the Spring Boot 2.0 course. I am working on the curriculum now but if you would like to receive updates check out my Spring Boot 2.0 Course Page and signup for updates. Anyone on this list will be the first to find out when it’s released and will receive a discount.
This is just the start of Spring 2.0 and we should have more exciting announcements to follow.
Question: What are you most looking forward to in Spring Boot 2.0?