Automate maven central release process

[jsajlovic]

Basic information

• nrich version: v1.1.0
• Module: project

Description

Summary

Implemented the Gradle Nexus Publish Plugin to completely automate the publish and release process to Maven Central. Automatic closing and releasing of "Nexus Staging Repositories" was not possible without this plugin.

Details

• added plugin to the project and configured it
• updated the publish GH action to use new Gradle tasks provided by the plugin

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Enhancement (non-breaking change which enhances existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix, enhancement or feature that would cause existing functionality to change in backward-incompatible way)
• Docs change
• Refactoring
• Dependency upgrade

Checklist

• I have read the project's CONTRIBUTING document
• I have checked my code with the project's static analysis tooling
• I have formatted my code with the project's IDEA code-style configuration
• I have checked my code for misspellings
• I have organized my changes in easy-to-follow commits
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests pass.