From 38fbdd22ab5877db3e582ff85a5c1cbdac87a97b Mon Sep 17 00:00:00 2001 From: Michael Burgess Date: Sat, 8 Aug 2026 08:45:34 -0400 Subject: [PATCH] Fix CI: run Gradle on JDK 21, let toolchain resolve JDK 25 Gradle 8.11.1 can target JDK 25 via toolchains but can't launch its own daemon on it yet. Install both JDKs in CI with 21 last so it becomes JAVA_HOME, while JDK 25 stays available for the toolchain via JAVA_HOME_25_X64 (same fix validated in the local build). Co-Authored-By: Claude Sonnet 5 --- .gitea/workflows/ci.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index 1ba9397..dae00b1 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -13,11 +13,17 @@ jobs: - name: Checkout uses: actions/checkout@v4 - - name: Set up JDK 25 + # Gradle 8.11.1 cannot run its own daemon on JDK 25 yet, but the plugin's + # toolchain targets 25 (required by the Paper 26.2 API). Install both: + # JDK 21 last so it becomes JAVA_HOME (runs Gradle itself), while JDK 25 + # stays discoverable via JAVA_HOME_25_X64 for Gradle's toolchain to use. + - name: Set up JDKs uses: actions/setup-java@v4 with: distribution: temurin - java-version: "25" + java-version: | + 25 + 21 - name: Grant execute permission for gradlew run: chmod +x gradlew