From bc106c3af9d3f062f8ca99bcf9501e4e9ffe10f8 Mon Sep 17 00:00:00 2001 From: denis0001-dev Date: Fri, 16 Oct 2026 18:53:59 +0300 Subject: [PATCH] Use setup-java's `path` output for FROMCHAT_PACKAGING_JDK setup-java@v5 names the installed JDK's location `path`, not `java-path` (the v4 name), so the beta4 run exported an empty value, fell back to the jmods-less /usr/lib/jvm/temurin-25-jdk-amd64 and failed with the same "can't find superclass or interface java.lang.Object" wall of warnings. The Gradle-side guard added in b0159eb correctly named the offending JDK in the beta4 log, which is what pointed at the empty export. --- .github/actions/setup-java-gradle/action.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/actions/setup-java-gradle/action.yml b/.github/actions/setup-java-gradle/action.yml index bfbdbd6..bba51dc 100644 --- a/.github/actions/setup-java-gradle/action.yml +++ b/.github/actions/setup-java-gradle/action.yml @@ -42,7 +42,7 @@ runs: - name: Export the jmods-capable desktop JDK if: inputs.desktop-jdk != '' shell: bash - run: echo "FROMCHAT_PACKAGING_JDK=${{ steps.desktop-jdk.outputs.java-path }}" >> "$GITHUB_ENV" + run: echo "FROMCHAT_PACKAGING_JDK=${{ steps.desktop-jdk.outputs.path }}" >> "$GITHUB_ENV" - uses: gradle/actions/setup-gradle@v5 with: