Spring Tools 5.4.0 Brings Claude Code Visualization and Faster Quick Fixes
Spring Tools 5.4.0 shipped on September 9, 2026, with new validations and quick fixes for common annotations including @ApplicationModuleListener, @SpringJUnitConfig, @RestController, and @Scope. These catch misconfigurations — like listener methods with the wrong signature, or scope annotations applied where they have no effect — at edit time instead of at runtime or during code review.
The more notable addition is Claude Code/MCP integration that lets the AI assistant visualize a project's logical module structure directly, which matters for anyone working in a Spring Modulith codebase where module boundaries aren't always obvious from file layout alone. The release also brings measurable performance work: the release notes describe "significant speedups around various quick fixes and repository-based version validation," plus more reliable source code indexing.
Spring Tools 5.4.0 supports Visual Studio Code, Cursor, Eclipse, Theia, and Claude Code, with the Eclipse-based distribution updated to track the 2026-09 Eclipse release train. The next release, 5.5.0, is scheduled for mid-December 2026.
Spring Modulith 2.2 M1 Moves to Spring Boot 4.2 and Framework 7.1
Spring Modulith shipped a coordinated release wave on August 26, 2026: milestone release 2.2 M1 alongside patch releases 2.1.1, 2.0.8, and 1.4.13. The headline change in 2.2 M1 is that it now tracks Spring Boot 4.2 M1 and Spring Framework 7.1 M1, keeping Modulith aligned with the leading edge of the Spring portfolio rather than trailing it.
2.2 M1 also brings improvements to the project's Namastack Outbox integration (used for implementing the transactional outbox pattern for reliable event publishing across module boundaries) and to how auto-configuration gets registered. Where applicable, these fixes were backported into the 2.1.1, 2.0.8, and 1.4.13 patch releases, which otherwise consist mainly of routine dependency upgrades.
For teams building modular monoliths with Spring Modulith, the Boot 4.2/Framework 7.1 alignment in 2.2 M1 is worth tracking now if you're planning an early adoption of the next Spring Boot minor line — it signals what module-boundary tooling will look like once 4.2 reaches GA.