Guillaume Nodet

Closing this one, I think the work has been done for 0.8.0. @hboutemy please reopen if needed.

> Is this really a follow-up? Instead, to me it seems like an alternative, more comprehensive solution than #413? Yes, the wording is wrong. I originally went to only extend...

This is related to https://github.com/mvndaemon/mvnd/issues/143 The main problem is that currently `mvnd` is tied to a specific maven version, because the maven cli is not extensible enough for `mvnd` and...

Could you try updating your setup to mvnd 0.8.0 which has been released a few days ago ? You'll find the binaries at https://downloads.apache.org/maven/mvnd/0.8.0/

@eforx any chance you could provide a way to reproduce the problem ?

Or at least provide a debug output to see if it contains anything useful.

Do you have a docker image to reproduce the problem ?

> Dockerfile add > _**RUN mkdir /lib64 && ln -s /lib/libc.musl-x86_64.so.1 /lib64/ld-linux-x86-64.so.2**_ Adding the link to the `musl` library still leads to an error: ``` ~ # ./mvnd-0.8.0-linux-amd64/bin/mvnd Error relocating...

> here a graalvm in alpine > https://github.com/renanpalmeira/docker-graalvm-alpine/blob/master/Dockerfile This looks a bit outdated as GraalVM location has changed (and version is now 22), but it may be used as a...

Unfortunately, we need to keep `mvn` distinct from `mvnd`, see https://github.com/mvndaemon/mvnd/pull/89