Evaluate and possibly use JReleaser

[msgilligan]

JReleaser looks nice!

It might be a good way of streamlining the Supernaut release process.

[aalmiray]

Link to the release doc is actually https://github.com/SupernautApp/SupernautFX/blob/master/doc/release-process.adoc

Looking at the doc I can say with confidence that JReleaser can take care of steps 1, 6, 7, and 10. The rest may be performed within a GH workflow or a GitLab CI pipeline.

Do you intend to publish Git releases to both Github and GitLab?

[msgilligan]

Do you intend to publish Git releases to both Github and GitLab?

I already removed publishing to GitHub last night (I really wasn't using it and it broke my release)

The next release will go to Maven Central.

[aalmiray]

OK, but where will you host the Git release? One thing is to release JARs and POMs to Maven Central (and GitHub Packages in the past), another is to have a Git release page (GitHub/GitLab) with matching tag, changelog, and perhaps release assets.

My question is on the latter.

[msgilligan]

OK, but where will you host the ... Git release page (GitHub/GitLab) with matching tag, changelog, and perhaps release assets.

Oh, sorry I misunderstood you. Release page will be on Github only.