MINOR: Upgrade gradle to 9.7.0

[serhiy-bzhezytskyy]

Update Gradle from 9.6.1 to 9.7.0, including the wrapper distribution
checksum and Kafka's wrapper JAR checksum references.

Followed the procedure in gradle/wrapper/README.md:

• gradle/dependencies.gradle — gradle version
• wrapper.gradle — wrapperChecksum
• gradle/wrapper/gradle-wrapper.properties and gradlew regenerated with
  ./gradlew wrapper --gradle-version 9.7.0 --distribution-type bin --gradle-distribution-sha256-sum <checksum>

Checksums are the published ones from https://gradle.org/release-checksums/:
binary distribution 84fbba45…873ae, wrapper JAR 7a9ce74c…62c5d.

The regenerated gradle-wrapper.properties also picks up retries=0 and
retryBackOffMs=500. Those are the WrapperConfiguration defaults which
9.7.0 now writes out explicitly, so behaviour is unchanged.

Verified locally with Gradle 9.7.0

• ./gradlew --version reports Gradle 9.7.0

Compile and artifacts

• ./gradlew compileJava compileTestJava
• ./gradlew jar
• ./gradlew srcJar
• ./gradlew testJar
• ./gradlew docsJar

Generated messages

• ./gradlew processMessages processTestMessages

Javadoc and scaladoc

• ./gradlew javadoc javadocJar
• ./gradlew scaladoc scaladocJar
• ./gradlew aggregatedJavadoc --no-parallel

Code quality

• ./gradlew clients:checkstyleMain clients:checkstyleTest clients:spotlessCheck
• ./gradlew clients:spotbugsMain -x test

Tests and publishing

• ./gradlew clients:test --tests RequestResponseTest
• ./gradlew -PskipSigning=true publishToMavenLocal

The build reports "Deprecated Gradle features were used in this build,
making it incompatible with Gradle 10." I ran the same tasks on 9.6.1 and
the set of reported deprecations is identical, so this is pre-existing and
not introduced here.

I did not run releaseTarGz, the full test suite, or the system tests
locally; leaving those to CI.

Following the MINOR: form used for the 9.6.1 bump in #23015, so no JIRA.

@dejan2609 you have been driving the Gradle and build-tooling updates
lately, so flagging this in case it overlaps with anything you have in
flight. @Parkerhiphop this follows your #23015 directly.

Reviewers: Dejan Stojadinović dejan2609@gmail.com, Parker Chang parkerhiphop027@gmail.com

[dejan2609]

Thank you for noticing my work @serhiy-bzhezytskyy !

At the moment I have three pending Gradle related PR's but none of them depends on a specific Gradle version.

All-in-all: go for it.

Note: I could provide some non-binding review in a few days (can't do that via mobile phone app) but hopefully some maintainer will pick this up sooner.

[serhiy-bzhezytskyy]

Thanks @dejan2609!

build / JUnit tests Java 17 (new) failed without running any tests — the job died fetching the Gradle distribution:

Attempt 1/1 failed. Reason: Unexpected end of file from server
Exception in thread "main" java.net.SocketException: Unexpected end of file from server
...
0 PASSED ✅, 0 FAILED ❌, 0 FLAKY ⚠️ , 0 SKIPPED 🙈, 0 QUARANTINED 😷, and 0 errors.

The exit code then comes from Parse JUnit tests, which had no results to read. The three sibling jobs on the same run (Java 17 flaky, Java 25 new, Java 25 flaky) passed.

The distribution itself is fine — I fetched gradle-9.7.0-bin.zip three times just now: 150,308,896 bytes each, sha256 84fbba45…873ae, matching the published checksum.

Could someone re-run the failed job when convenient?

[dejan2609]

Could someone re-run the failed job when convenient?

@serhiy-bzhezytskyy
Small hint: just rebase PR branch onto current trunk (or amend commit without changing anything) and GitHub Actions will execute all jobs 💡

(Not sure is there an option to rerun only failed jobs; maybe maintainers could do that)

[Parkerhiphop]

@serhiy-bzhezytskyy Thanks for the update and following up!

The current failures look like flaky tests. I agree with @dejan2609 that you can sync with trunk and push a merge commit to re-trigger the CI.

That's usually how I handle these CI failures too.

[dejan2609]

Two new entries in gradle/wrapper/gradle-wrapper.properties are completely legit (they are introduced since Gradle version 9.5.0):

retries=0
retryBackOffMs=500

Related links:

• gradle/gradle@3b76aaa Add retries and timeout for gradle download
• gradle/gradle@f9ea3b1 Rename 'retryTimeoutMs' to "retryBackOffMs"
• https://docs.gradle.org/9.7.0/userguide/gradle_wrapper.html#sec:configuring_wrapper_retries
• https://docs.gradle.org/9.7.0/javadoc/org/gradle/api/tasks/wrapper/Wrapper.html#getRetries()

I did some testing:

• Kafka distribution created using ./gradlew releaseTarGz
• cluster started, events written into topic, events being read -->> everything works fine ✔️ (test scenario: https://kafka.apache.org/quickstart)

@serhiy-bzhezytskyy 💡 Hint: bump Gradle version to 9.7.1 that will be released in a next few days: https://github.com/gradle/gradle/milestone/352?closed=1

Overall: LGTM (non-binding) ✅