[Feature Request]: Upgrade Gradle wrapper to 9.x for JDK 25 support

Open
  • Is something wrong?
#40,556 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
build-system

Research direction

The change is the Gradle wrapper version, currently 8.14.3, so start from the wrapper configuration and the build scripts that depend on it. Read the linked toolchain work (#35627 and #36409) to see how JDK 25 is already handled, then check which build plugins and dependencies fail on Gradle 9. Done means the wrapper runs on JDK 25 without org.gradle.java.home set and the existing build and tests still pass.

Written by the indexing model from the issue text.

Description

awaiting triage java new feature P2
What would you like to happen?

Currently, Beam uses Gradle Wrapper 8.14.3.

While Beam already supports compiling and running tests against JDK 25 via Gradle Java Toolchains (#35627 / #36409), the Gradle daemon itself cannot run directly on JDK 25 in Gradle 8.x. Running ./gradlew on a machine where the system default JAVA_HOME is JDK 25 fails at startup unless org.gradle.java.home is manually pointed to an older JDK (like 17 or 21).

To provide an out-of-the-box developer experience on systems with JDK 25 as the default runtime, we should track upgrading the Gradle wrapper to Gradle 9.x (which natively supports running the daemon on JDK 25) once Beam's build plugins and dependencies are compatible with Gradle 9.

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components
  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Prism Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Dominant language
Java
Stars
8.7k
Forks
4.8k
Avg merge
2d 9h
Merged PRs (30d)
368

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/beam

All issues in apache/beam

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.