CI: Use Maven wrapper instead of system mvn #25

New Issue

2026-03-27T15:57:47Z

thib8956 commented

2026-03-27 15:57:47 +00:00

The CI pipeline fails with mvn: command not found (exit code 127) because the Gitea runner image docker.gitea.com/runner-images:ubuntu-latest does not ship Maven pre-installed (unlike GitHub-hosted runners).

Fix: add the Maven wrapper (mvnw + .mvn/wrapper/) to the repo and use ./mvnw in the CI workflow instead of mvn.

The CI pipeline fails with `mvn: command not found` (exit code 127) because the Gitea runner image `docker.gitea.com/runner-images:ubuntu-latest` does not ship Maven pre-installed (unlike GitHub-hosted runners). Fix: add the Maven wrapper (`mvnw` + `.mvn/wrapper/`) to the repo and use `./mvnw` in the CI workflow instead of `mvn`.

thib8956 referenced this issue from a commit

2026-03-27 15:58:12 +00:00

fix(ci): use Maven wrapper instead of system mvn

thib8956 referenced a pull request that will close this issue

2026-03-27 15:58:24 +00:00

fix(ci): use Maven wrapper instead of system mvn #26

thib8956 closed this issue

2026-03-27 16:09:54 +00:00

Sign in to join this conversation.