Key Changes in Spring Boot 3.0.0 M1: Java 17 Baseline, Jakarta EE Migration, and Dependency Updates
Spring Boot 3.0.0 M1 introduces a Java 17 baseline, requires migration of all Java EE APIs to Jakarta EE, removes support for several third‑party libraries, updates numerous Spring project dependencies, and outlines the upcoming release cadence, while also highlighting community resources and promotional offers.
Spring Boot 3.0.0 M1 was announced with several major changes. The baseline Java version has been upgraded from Java 8 to Java 17, signaling the shift to the newer language features.
All Java EE APIs now need to be migrated to Jakarta EE. For example, imports such as javax.servlet.Filter must be replaced with jakarta.servlet.Filter .
Some third‑party libraries that depend on Java EE APIs are temporarily removed from Spring Boot 3.0.0 M1, including EhCache 3 , Infinispan , Jolokia , and Pooled JMS . Additionally, the following components are no longer supported in this milestone:
Apache ActiveMQ
Atomikos
EhCache 2
Hazelcast 3
The milestone also updates the versions of many Spring projects and related dependencies. Notable Spring dependency versions are:
Micrometer 2.0.0‑M1
Spring AMQP 3.0.0‑M1
Spring Batch 5.0.0‑M1
Spring Data 2022.0.0‑M1
Spring Framework 6.0.0‑M2
Spring Integration 6.0.0‑M1
Spring HATEOAS 2.0.0‑M1
Spring Kafka 3.0.0‑M1
Spring LDAP 3.0.0‑M1
Spring REST Docs 3.0.0‑M1
Spring Security 6.0.0‑M1
Spring Session 2022.0.0‑M1
Spring Web Services 4.0.0‑M1
Third‑party library versions have also been updated, covering Jakarta Activation, Jakarta Annotation, Jakarta JMS, Jakarta JSON, Jakarta Servlet, Jetty, jOOQ, and more.
The Spring Boot team plans to release a new milestone every two months, continuing the rapid evolution of the framework.
Top Architect
Top Architect focuses on sharing practical architecture knowledge, covering enterprise, system, website, large‑scale distributed, and high‑availability architectures, plus architecture adjustments using internet technologies. We welcome idea‑driven, sharing‑oriented architects to exchange and learn together.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.