Git Build Hook Versions Save

Adds the following skip parameters to allow users to skip the use of a particular Mojo during the build;

• gitbuildhook.init.skip
• gitbuildhook.install.skip
• gitbuildhook.gitconfig.skip

• Speculative fix for thread safety issues.

• Fixed and issue where the configure goal would fail when running the plugin in a git worktree. Changing the configure goal configuration in a worktree will not take affect until a build is run with those changes outside of the worktree.
• The readonly attribute (which shouldn't have been there in the first place) was removed from some goal parameters. This removes some annoying warnings from the build output.
• Temporary test artefacts from development of this plugin will not longer be deployed to Maven Central with the main artefact.

Added support for all hooks that exist as of Git 2.37.2.

Improvements

• Makes the initialize goal thread safe.
• Mark the initialize and configure goals thread safe for Maven builds to prevent associated warning messages when running multi-threaded builds.

New Features

• Pull in specific hooks into the default hooks directory from the classpath rather than from the project directory.
• Add support for pre merge hooks.

Improvements

• The configure goal has been generalized and will now set any git config on your project you like, rather than just the core.hooksPath configuration.
• Both the configure and install goals have moved their maven plugin configuration moved into their own elements to separate them from each other. Please see the updated README for more details.

Migration

• The legacy configuration for both configure and install will not be supported for 3.0.0, and so you will need to update your plugin configuration when updating to this version

Add a new goal configure, which allows you to leverage the ability in Git to specify a custom directory for your hooks. It is now described as the default way of using the plugin in the documentation.

Reduce the per-requisite Maven version to 3.0.0

A bug was identified where replaying an existing hook would fail. This has been corrected. The git hooks specified in the plugin configuration will now be replaced every time the build is run with the specified file. Updates to this file will now be transferred to the applied hook with each build.