107 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-01
stories 33

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

SPRING ALIGNMENT: FIVE PROJECTS SYNC BUILD SYSTEMS WITH COMMERCIAL REPOS

By RepoJournal · Filed · About Spring · Composed from the cited sources · methodology

Spring Integration, Kafka, and AMQP are restructuring their Gradle builds to run identically in both open-source and commercial repositories, a significant operational shift across the portfolio.

The alignment spans three core projects. Spring Integration [1], Spring Kafka [3], and Spring AMQP [4] have all relocated their Maven publishing configuration to the repository root and wrapped it in `allprojects`, collapsing multiple build.gradle apply statements into a single call that matches the commercial repo layout. This move eliminates friction when the same workflow files and scripts need to run unmodified across both repositories, a pattern that signals tighter integration between open-source and commercial builds going forward. Spring Security is tightening its own error handling: the framework now fails fast with a clear IllegalStateException when spring-security-access is missing from the classpath [2], rather than throwing a cryptic NoClassDefFoundError at startup. The change stems from refactoring work that moved MethodSecurityMetadataSourceAdvisor and MethodSecurityInterceptor into the optional spring-security-access module, exposing a gap when legacy method-security support runs without it. Spring Integration 7.2.0 is underway with upgrades across Gradle 9.6.1, Checkstyle 13.8.0, Jackson 3.2.1, gRPC 1.83.1, MongoDB driver 5.9.1, and others [6]. AMQP is launching 4.2.0 with parallel dependency bumps including Kotlin 2.4.10, Checkstyle 13.8.0, Jackson 2.22.1 and 3.2.1, RabbitMQ client 1.2.0, and stream client 1.8.0 [7]. Spring Tools fixed a logging regression where intentional cache cancellation was being wrapped in CompletionException and logged as an error [5]; the fix unwraps only that exception before checking for cancellation, preserving error logging for real failures.

Action items

References

  1. [1] Align with commercial build support ↗ spring-projects/spring-integration
  2. [2] Fail fast when spring-security-access is missing ↗ spring-projects/spring-security
  3. [3] Align with commercial build support ↗ spring-projects/spring-kafka
  4. [4] Align with commercial build support ↗ spring-projects/spring-amqp
  5. [5] Avoid logging expected cache cancellation (#1953) ↗ spring-projects/spring-tools
  6. [6] Start `7.2.0` version ↗ spring-projects/spring-integration
  7. [7] Start `4.2.0` in `main` ↗ spring-projects/spring-amqp

Quick answers

What shipped in Spring on August 1, 2026?
Spring Integration, Kafka, and AMQP are restructuring their Gradle builds to run identically in both open-source and commercial repositories, a significant operational shift across the portfolio. In total, 25 commits and 8 pull requests landed.
Who contributed to Spring on August 1, 2026?
8 developers shipped this update, including ziplla, Martin Lippert, BoykoAlex, Artem Bilan, Glenn Renfro, Josh Cummings, jyx-07, and sobychacko.
What were the notable Spring updates?
Align with commercial build support, Fail fast when spring-security-access is missing, and Align with commercial build support.