Skip to content

Bump Java baseline to 25 on master#8893

Open
reiabreu wants to merge 1 commit into
masterfrom
java25-baseline
Open

Bump Java baseline to 25 on master#8893
reiabreu wants to merge 1 commit into
masterfrom
java25-baseline

Conversation

@reiabreu

@reiabreu reiabreu commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bumps javaVersion in pom.xml from 21 to 25
  • Updates the maven.yaml CI build job to use JDK 25 and drops Java 21 from the test matrix (now runs exclusively on 25)
  • Updates nightlies.yaml, snapshots.yaml, and update-license-files.yml to use JDK 25

Motivation

Java 25 is the next LTS after 21. The key driver is JEP 491 ("Synchronize Virtual Threads without Pinning"), delivered in Java 24 and carried into the 25 LTS. Before this fix, virtual threads blocked inside synchronized blocks would pin their carrier thread — under load this could exhaust the carrier pool. On Java 25 the VT unmounts cleanly while waiting, which removes the main blocker for adopting virtual threads in Storm's I/O-bound paths (Netty transport, bolt external calls, ZK/Nimbus heartbeat paths) without first rewriting every synchronized block to ReentrantLock.

This was discussed on the dev@ list as part of the 3.0.0 planning thread.

Test plan

  • CI passes on JDK 25 (maven.yaml build + test matrix)
  • Nightly and snapshot workflows resolve JDK 25 via Temurin without error

🤖 Generated with Claude Code

Move master off Java 21 and onto Java 25 (LTS) as the exclusive build
and test JDK. The main motivation is JEP 491, which landed in Java 24
and is carried into the 25 LTS: virtual threads no longer pin their
carrier when blocking inside a synchronized block, removing a key
constraint on adopting VTs in Storm's I/O-bound paths.

Changes:
- pom.xml: javaVersion 21 → 25
- maven.yaml: build job uses JDK 25; test matrix drops 21, keeps only 25
- nightlies.yaml, snapshots.yaml, update-license-files.yml: JDK 21 → 25

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant