github-actions[bot] commented on code in PR #41376:
URL: https://github.com/apache/beam/pull/41376#discussion_r4582014599


##########
gradle/wrapper/gradle-wrapper.properties:
##########
@@ -1,6 +1,6 @@
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-8.14.3-bin.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-9.9.1-bin.zip

Review Comment:
   **🔴 Critical**: Bumping `gradle-wrapper` to `9.9.1` without migrating 
`buildSrc` and project build scripts breaks the entire Gradle build (all Gradle 
PreCommit checks fail at configuration/compilation time). Specifically:
   
   1. **Removed APIs in `buildSrc` and build scripts:** `Project.exec` / 
`Project.javaexec` (`build.gradle.kts`, `BeamModulePlugin.groovy`), 
`AbstractArchiveTask.archivePath`, `Report.enabled`, and legacy convention 
properties (`archivesBaseName`, `mainClassName`, `sourceCompatibility`, 
`targetCompatibility`, `reportsDir`) have been removed in Gradle 9.
   2. **Incompatible plugins in `buildSrc/build.gradle.kts` and 
`build.gradle.kts`:** `com.google.protobuf:protobuf-gradle-plugin:0.8.13`, 
`com.github.spotbugs.snom:spotbugs-gradle-plugin:5.0.14`, 
`org.checkerframework:checkerframework-gradle-plugin:0.6.56`, and 
`org.sonarqube:3.0` rely on removed Gradle APIs.
   3. **JDK 17+ requirement:** Gradle 9 requires Java 17+ to run the daemon.
   
   This PR should be closed until the Gradle 9 migration (#40556) is completed. 
Using `@dependabot ignore this major version` (or ignoring 
`version-update:semver-major` for `gradle-wrapper` in `.github/dependabot.yml`) 
will prevent Dependabot from reopening PRs for subsequent `9.x` releases.
   
   ```suggestion
   
distributionUrl=https\://services.gradle.org/distributions/gradle-8.14.3-bin.zip
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to