Add support for local maven deployment

[jerboaa]

Example usage which installs the current version into the local maven repo (~/.m2 on Linux):

$ java -ea ./build.java --maven-deploy-local --mandrel-version $MANDREL_VERSION --verbose --mx-home $MX_HOME --mandrel-repo $MANDREL_REPO --mandrel-home $MANDREL_HOME

Closes: #354

[zakkak]

The PR looks good to me but I wonder if it's really necessary.

Can't you achieve local deployment with --maven-repo-id local --maven-version 3.6.0 --maven-url file://$HOME/.m2/repository

[jerboaa]

Thanks for the review! Don't merge this just yet (still some things coming).

Can't you achieve local deployment with --maven-repo-id local --maven-version 3.6.0 --maven-url file://$HOME/.m2/repository

It's a mvn deploy vs. mvn install call. I'd prefer an install so as to not even attempt to go remote. Also using the internal install logic frees us from trying to re-dediscover the local repo and all that.

[jerboaa]

@zakkak Please review again. graalvm/mandrel#526 (comment) contains a draft as to where this is going.

[zakkak]

Still LGTM, just added two minor comments.

[github-actions]

This PR appears to be stale because it has been open 30 days with no activity. This PR will be closed in 7 days unless Stale label is removed or a new comment is made.

[jerboaa]

These four sub-modules need to be added to the deploy artifacts list, since otherwise only GRAAL_SDK gets deployed to the local maven repo and its dependencies won't get resolved properly (as they're not in the local repo). This is in-line with the graal-sdk artefact split.

[jerboaa]

This PR depends on #360

[zakkak]

LGTM thanks @jerboaa

[jerboaa]

CI passes with this in the 23.1 branch. See https://github.com/jerboaa/mandrel-packaging/actions/runs/6099726559

I'm merging this.