mvnd in the maven wrapper in teams

[nielsbasjes]

When I want to use the mvnd in the maven wrapper I can simply specify the download url and it works.

However because mvnd is only distributed as native executables I have a problem when working in a team (or opensource project) where people have different hardware. Some have Arm based Macs, some still have an old intel based mac and I normally work on an x86_64 based Linux.

I would like to use mvnd but at this time I cannot make it part of the mvn wrapper config in the projects.

So although a non-graalvm distribution of mvnd is slower, it is desirable for situations like this.

[Blacktiger]

Maven builds can sometimes be sensitive to the version of maven used. Maybe it would be worth providing some way to configure mvnd to use a specific maven version already installed on the system? Then if you're using the maven wrapper you could just configure mvnd to point to the wrapper so you still get the benefits of having the daemon running in the background? I suppose mvnd has to hook deeply into maven itself so maybe that won't work?