The Wire · Showcase
SPRING FRAMEWORK AND BOOT PURGE DEPRECATION WARNINGS AHEAD OF GRADLE 10
By RepoJournal · Filed · About Spring
Spring Framework is systematically eliminating deprecation warnings across the codebase as Gradle 9.6 forces the migration to modern APIs.
The framework team addressed internal and public deprecations spanning deprecated Locale constructors, URL constructors, and Thread#getId calls [1]. This cleanup is tied to a Gradle upgrade that's already emitting warnings of its own. The Gradle 9.6.0/9.6.1 jump deprecated Project.getProperties() and will remove it entirely in Gradle 10.0, forcing Spring Framework to migrate TestConventions and build scripts to use findProperty() instead [2]. Over in Boot land, the team is squashing a trio of bugs where Actuator fails to refresh on Jersey and Cloud Foundry when spring-boot-health is absent [3] [4]. The fix moves health-specific beans into nested configurations so management endpoints can load without the health module present [5]. Meanwhile, OpenTelemetry documentation got clarified on service.name and service.namespace defaults [6].
Action items
- → Review your Gradle plugin usage if you're on 9.6+, Spring Framework has already patched the deprecations spring-projects/spring-framework [plan]
- → If running Boot Actuator on Jersey or Cloud Foundry without health module, verify your context refresh works after this patch spring-projects/spring-boot [monitor]
References
- [1] Address deprecation warnings spring-projects/spring-framework
- [2] Avoid Gradle deprecation warnings spring-projects/spring-framework
- [3] Context refresh fails when using Actuator on Jersey without spring-boot-health ↗ spring-projects/spring-boot
- [4] Context refresh fails on Cloud Foundry when using Actuator without spring-boot-health ↗ spring-projects/spring-boot
- [5] Avoid loading health classes in Jersey config spring-projects/spring-boot
- [6] Update OpenTelemetryResourceAttributes documentation spring-projects/spring-boot
FAQ
- What changed in Spring on June 28, 2026?
- Spring Framework is systematically eliminating deprecation warnings across the codebase as Gradle 9.6 forces the migration to modern APIs.
- What should Spring teams do about it?
- Review your Gradle plugin usage if you're on 9.6+, Spring Framework has already patched the deprecations • If running Boot Actuator on Jersey or Cloud Foundry without health module, verify your context refresh works after this patch
- Which Spring repositories shipped on June 28, 2026?
- spring-projects/spring-framework, spring-projects/spring-boot