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.
This commit is contained in:
2026-10-16 18:53:59 +03:00
Unverified
parent b0159eb987
commit bc106c3af9
+1 -1
View File
@@ -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: