kevin
e32ac39faf
CI / build (push) Failing after 2m1s
First CI run failed at 'Build and test' with exit code 127 (command not found): actions/setup-java@v4 provisions a JDK but not Maven, and the runner image has no mvn on PATH. The sibling lms/alms workflow apt-installs both; this workflow switched to setup-java for JDK 25 (the image's default-jdk is too old for maven.compiler.release=25) and dropped the maven install with it. Adds an explicit Maven install with Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) Maven home: /Users/appbuilder/Tool/apache-maven-3.9.16 Java version: 25.0.2, vendor: Oracle Corporation, runtime: /Users/appbuilder/Tool/jdk-25.0.2.jdk/Contents/Home Default locale: en_VN, platform encoding: UTF-8 OS name: "mac os x", version: "26.5.1", arch: "aarch64", family: "mac" so the log proves which JDK it resolved — JAVA_HOME from setup-java must win over the JRE apt drags in.