What’s New in Spring Boot 2.5? Features, Dark Mode & Key Changes
Spring Boot 2.5.0 (alongside 2.4.6 and 2.3.11) introduces Java 16 support, Gradle 7 compatibility, enhanced Docker image building, a new datasource loading mechanism, dark‑mode documentation, and several important configuration and security changes for backend developers.
Spring Boot 2.5.0, 2.4.6, and 2.3.11 have been officially released.
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.5.0</version>
</parent>New Features
Support for Java 16
Support for Gradle 7
Enhanced Docker image building tools
Brand‑new datasource loading mechanism
Detailed explanations of Spring Boot 2.5’s new features can be found in the previous posts of the “JAVA Architecture Diary” public account.
Dark Mode
Fresh appearance with clearer fonts.
Expandable/collapsible example code arrows for import and detail display.
Code snippet clipboard button.
Documentation supports dark mode.
Important Changes
Datasource related changes: spring.datasource.* has been replaced by spring.sql.init.* properties.
Flyway and Liquibase now require separate username and password settings; they no longer inherit from the datasource.
Spring Data Solr is no longer maintained and has been removed from the source.
The /info endpoint is no longer exposed via the web; if the class includes Spring Security, authentication is required.
EL syntax implementation has switched from tomcat-embed-el to jakarta-el.
Error view pages no longer contain detailed error messages by default; they can be enabled with server.error.include-message.
Logging resources can be released on JVM shutdown by setting logging.register-shutdown-hook.
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 Architecture Diary
Committed to sharing original, high‑quality technical articles; no fluff or promotional content.
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.
