The Wire · Showcase
SPRING BOOT LOCKS DOWN TEST REGISTRY BEHAVIOR, SPRING TOOLS 5.3 SHIPS WITH STABILITY FIX
By RepoJournal · Filed · About Spring
Spring Boot adds automatic test isolation for Micrometer's global registry, while Spring Tools 5.3 lands critical fixes for boot MCP crashes and Eclipse AOT errors.
Spring Boot merged a follow-up to an earlier request that disables the global Micrometer registry in tests by default [1]. The change introduces a new `DisableGlobalMeterRegistryContextCustomizerFactory` that mirrors the existing Reactor pattern, leaving explicit configuration values untouched. This surfaces test isolation as a first-class concern without breaking existing setups.
Spring Tools shipped 5.3.0.RELEASE with three major improvement buckets [2]. The Boot validation layer now catches false positives, inner record bean misdetection, and native query checks. The team modernized from RestTemplate to RestClient and scrubbed legacy dependencies. Most critically, the release resolves Boot MCP startup crashes, Eclipse AOT errors, and JMX connection bugs that were blocking adoption.
Spring Framework continues its security hardening and API cleanup work [3] [4]. HandlerMappingIntrospector is now removed as promised, and DataBinder's `setDisallowedFields` method is deprecated in favor of safer alternatives [5]. Documentation on SpEL lifecycle and the security implications of untrusted expression evaluation landed to prevent production surprises [11].
Spring Data Redis and Spring Session absorbed routine maintenance: a parser-bound deserialization context fix for type hints [6] and MariaDB connector bumps to 3.5.10 across two session branches [7] [8]. Spring Tools itself merged stream consumption fixes for build commands to prevent process hangs [9] and added YAML alias/anchor cycle support [10].
One email a day. Unsubscribe in one click.
Keep up with Spring in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review Spring Boot's new test registry defaults in your integration tests spring-projects/spring-boot [plan]
- → Upgrade to Spring Tools 5.3.0 if you use Boot MCP or Eclipse AOT spring-projects/spring-tools [immediate]
- → Audit any DataBinder.setDisallowedFields usage before Spring Framework 6.3 spring-projects/spring-framework [plan]
References
- [1] Disable Micrometer global registry in tests by default ↗ spring-projects/spring-boot
- [2] 5.3.0.RELEASE ↗ spring-projects/spring-tools
- [3] Remove HandlerMappingIntrospector spring-projects/spring-framework
- [4] Deprecate setDisallowedFields in DataBinder spring-projects/spring-framework
- [5] Document security implications of evaluating untrusted SpEL expressions spring-projects/spring-framework
- [6] Use Parser-bound `DeserializationContext` for parsing type hints in `TypeResolver`. spring-projects/spring-data-redis
- [7] Bump org.mariadb.jdbc:mariadb-java-client from 3.5.9 to 3.5.10 ↗ spring-projects/spring-session
- [8] Bump org.mariadb.jdbc:mariadb-java-client from 3.5.9 to 3.5.10 ↗ spring-projects/spring-session
- [9] Consume output and error streams for build command process (#1952) spring-projects/spring-tools
- [10] Support cycles in YAML AST via aliases/anchors (#57) spring-projects/spring-tools
- [11] Document lifecycle and reuse contract for SpEL expressions and contexts spring-projects/spring-framework