* Use muti-release jar to fallback mvnd-client to original maven
The mvnd-client is built to a muti-release jar. The default version of
DefaultClient is compiled against the same target version as the
embedded maven (4.x, so JDK 1.8) which only invoke the MavenCli.main().
The java-11 version is the full qualified mvnd-client.
* update cmd scripts
* embedded maven now works under JDK 1.8
Build SimpleAppender for JDK 1.8 since it is the log appender only
for the embedded maven
Co-authored-by: Guillaume Nodet <gnodet@gmail.com>
# Conflicts:
# pom.xml
* Improve reproducibility of builds by using digest on docker images
* Inline the manifest Multi-Release entry
* Remove unused files
* Switch the groupId to org.apache.maven.daemon and use maven parent pom
* Fix distribution
* Fix ITs
* Fix native build for windows
* Update mvnd to include Maven Resolver 1.7
As mvnd itself is Java8 lang level, it is completely
okay to up resolver to 1.7 (that is java8 as well).
The only reason why Maven 3.8.x CANNOT use resolver
1.7 is that it is still Java7 level.
* Move missing piece to SPI
* Add global exclusions
* Example of mvnd using file locking (of resolver)
* Drop irrelevant
* Upgrade to released 1.7.3
Co-authored-by: Guillaume Nodet <gnodet@gmail.com>
* Refactor early-access builds with JReleaser
* Add brew and sdkman to release configuration
* Tweak changelog generation
* Do not trigger verify workflow when changelog is updated
* Add release workflows
* Exclude template files from license check
* configure access tokens for Homebrew and Sdkman
* Fix Graal settings in workflows
* setup-graalvm takes care of adjusting the environment on Windows
* Fix workflow configuration
* Uncoment sdkman settings in workflow
* Remove explicit JReleaser build from workflows
* Configure SCM urls
* Update to JReleaser 1.0.0-M1
* Update to JReleaser 1.0.0-RC2
* Update to JReleaser 1.0.0
