Spring Boot 3.0 RC1 Released with Native Image Support and Jakarta EE 9 Migration
Spring Boot 3.0 RC1 introduces 135 enhancements, native executable support via Maven/Gradle plugins, migration to Jakarta EE 9, Java 17 baseline, and new features such as flexible Spring Data JDBC auto‑configuration, Prometheus example auto‑configuration, and Log4j2 improvements, with full details in the release notes.
Spring Boot 3.0 RC1 has been released, bringing 135 enhancements, documentation updates, dependency upgrades, and bug fixes.
The release adds support for building native executables with the standard Spring Boot Maven or Gradle plugins, based on GraalVM, without special configuration.
New documentation explains AOT processing and guides users to generate their first GraalVM native image.
Spring Boot 3.0 also completes migration to Jakarta EE 9 and upgrades the baseline Java version to Java 17.
Additional features include more flexible auto‑configuration for Spring Data JDBC, auto‑configuration for Prometheus examples, and enhanced Log4j2 support such as configuration file handling and environment property lookup.
For full details see the release notes at https://github.com/spring-projects/spring-boot/releases/tag/v3.0.0-RC1.
Spring Boot 2.7.5 and 2.6.13 contain mainly bug fixes, documentation improvements, and dependency upgrades; see their respective release notes.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java Captain
Focused on Java technologies: SSM, the Spring ecosystem, microservices, MySQL, MyCat, clustering, distributed systems, middleware, Linux, networking, multithreading; occasionally covers DevOps tools like Jenkins, Nexus, Docker, ELK; shares practical tech insights and is dedicated to full‑stack Java development.
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.