What’s New in Spring Boot 2.2.2? Key Features and Bug Fixes Explained
Spring Boot 2.2.2 introduces ConstructorBinding enhancements, Gradle 6 support, and a series of bug fixes ranging from @SpyBean scope issues to Liquibase endpoint inaccuracies, providing developers with clearer configuration handling and improved stability across the framework.
Spring Boot 2.2.2 has been released with the following updates:
New Features
Enhanced ConstructorBinding , supporting nested class constructor property injection.
Support for Gradle 6 .
Bug Fixes
@SpyBean (MockitoPostProcessor) initialization of @StepScope bean out-of-bounds issue.
When configuring Netty, the server.ssl.key-alias property is ignored.
Using @Validated on immutable configuration property classes (with @ConstructorBinding) does not display the property in actuator.
Bean class placeholder does not work in 2.2.1.RELEASE: class="${service.class}" .
Liquibase endpoint fails to provide correct information when using multiple data sources.
ConstructorBinding fails when configuration class has a Map type parameter.
Rabbit configuration without protocol in address ignores ssl.enabled.
Spring Boot DevTools YAML property loading does not work (issue #19081).
Permission configuration is correct, but HealthWebEndpointMapper shows all endpoints as fresh.
Spring Boot Maven plugin shutdown issue (issue #18940).
BasicJsonParser cannot correctly handle spaces between [ and {.
@ServletComponentScan does not work with component index feature.
For more version upgrades, refer to the official release notes: https://github.com/spring-projects/spring-boot/releases/tag/v2.2.2.RELEASE
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.
