Use mvnd in GitHub Actions

[adamretter]

Builds atop #4917 to switch CI from using mvn to mvnd (i.e. Maven Daemon)

[adamretter]

I am aware that connecting to the Maven Daemon in Windows and macOS runners seems to intermittently fail even though I have provided a generous timeout of 90 seconds. I have made enquiries about that here - apache/maven-mvnd#772 (comment)

[dizzzz]

LGTM

[dizzzz]

OK to pull?

[duncdrum]

@dizzzz as long as the problems with mavend on win and macOS persist, I d say no. Otherwise we give up testing on the list of supported platforms.

The config changes do not depend on mavend. We either wait for things to get sorted out upstream with mavend or create a new PR without mavend

[reinhapa]

@dizzzz as long as the problems with mavend on win and macOS persist, I d say no. Otherwise we give up testing on the list of supported platforms.

The config changes do not depend on mavend. We either wait for things to get sorted out upstream with mavend or create a new PR without mavend

@duncdrum as far as I can see do the actual test pass on Windows, "only" the coverage part fails with a timeout... I'm in the process to check that build on my Windows instance at the moment...

[duncdrum]

@reinhapa unfortunately the mavend time-out linked above occurs on the start of ci run, so the test won’t run.

If that issue has been fixed good to merge, but otherwise we should still hold, otherwise we risk PRs with stuck runs on both win and macOS

[adamretter]

I separated the non-mvnd related changes out into a new PR (which should be merged first) - #4917

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[dizzzz]

I missed the latest changes, my apologies. It looks OK to me right now!