Java build failed: Gradle command unavailable in Maven container
Error recorded 2 times in PanelAlpha Engine deploys on Java. The deploy log below is the recorded failure output.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen2 times · 2 variants
WhereJava
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Java strategy selected a Maven container, but the build then invoked gradle, which is not installed there. The repository contains both Maven and Gradle manifests, while detection selected the Gradle strategy even though pom.xml was the selected application file. The build container also reported that /root and its Maven cache were not writable.
What the log looks like
Deploy log
Compiling application on hostUnable to find image 'maven:3-eclipse-temurin-21' locallyStatus: Downloaded newer image for maven:3-eclipse-temurin-21mkdir: cannot create directory ‘/root’: Permission deniedCan not write to /root/.m2/copy_reference_file.log. Wrong volume permissions? Carrying on ...sh: 1: gradle: not foundDeploy failed