Publishing to central.sonatype.com

[dr0i]

(Substitues #677).

From #677 (comment):

There is no change regarding the Gradle Nexus Publish Plugin, only on Sonatype's side. And the plugin we've been using should be able to handle that with some configuration.

[dr0i]

As discussed : @blackwinter will set the proper config and @TobiasNx and @dr0i will test it by making a release.

[blackwinter]

Since I'm unfamiliar with the Sonatype/Maven Central release process, I'm not really sure which changes are actually required (might also depend on when the account was registered and/or whether the namespace has already been migrated?). But there is a step-by-step guide on how to successfully publish a release using the Gradle Nexus Publish Plugin (see also the follow-up comments). So I think it might be our best option to try it out during the next release (#713) and make adjustments as necessary (see also the plugin documentation and the Sonatype documentation). I can join in on the actual deployment to offer support during the process.