Reconfigure Maven release process without org.sonatype.oss:oss-parent:9

org.sonatype.oss:oss-parent:9 is deprecated:

In the past all the plugin configuration and other setup was managed by a Maven parent POM with the latest coordinates of org.sonatype.oss:oss-parent:9. This project leaked SCM, URL and other details and its usage is discouraged. Maintenance of the project has stopped and it no longer works with latest tooling such as Maven versions or Java versions. If desired, please manage your own organization-level POM in a similar manner.

See https://central.sonatype.org/pages/apache-maven.html for details.

[gotson]

The one use case i find interesting for publishing snapshots is for people to confirm an issue is fixed after you did commit a fix, but didn’t cut a release yet. That’s especially true for people who don’t know how to build a project from source, publish it to maven local, then use that in their own project.

Up to you to publish snapshots, i’ve just tried it, it takes ~5 minutes to perform the publish of all the artifacts. See published result.

[gotson]

Indeed the parent POM contains the signing plugin. I can propose a PR that would perform automatic pushes to OSSRH, which would be done on snapshots repository for *-SNAPSHOT versions, and to Maven Central for proper versions. You could keep doing the commits to set the version before a release, and the CI would do the deployment.

PS: There’s also a PR for moving the CI from Travis to GH Actions. I don’t expect you to finish that, but just keep It in mind. 😀

I was looking at that also 🙃