Publish to mavencentral

[JeroenMols]

⚠️ This code must still be tested before merging ⚠️

Open items to do:

• Create Streem Sonatype account
• Add SONATYPE_API_USER and SONATYPE_API_KEY as Github actions secrets
• Create Streem PGP key and publish it on a public key server
• Add SONATYPE_PGP_KEY_BASE64 as Github actions secret (export key using gpg --export-secret-key --armor | base64)
• Look into how to support snapshots
• Test upload to Maven Central

---

This PR converts all existing plumbing to upload to Maven Central instead of Bintray. Key changes are:

1. Rename all Bintray/JCenter references to Sonatype/Maven Central
2. Change maven URL
3. Add artifact signing
4. Update pom.xml so it contains all required attributes for Maven Central (see here https://central.sonatype.org/publish/requirements/#sufficient-metadata)

I've taken this as far as I can take it, for the next steps credentials/signing keys are needed so I'd like for someone else to take over.

Finally note that I was unable to test run publishToMavenCentralRepository as Gradle can't find the task. Not sure why, but the same was already happening for publishToBintrayRepository so I decided to ignore that.

Relates to #120

[JeroenMols]

See placeholder above so we don't forget to update this link

[JeroenMols]

I checked and this issue still seems to exist

[garyp]

Thanks for starting this! I had your blog post about migrating to Maven Central up in my browser and was trying to find time to work on it 😄 I had already created a Sonatype account a few weeks ago and went through the process to get approved for artifacts under the pro.streem namespace. I've added the credentials as secrets in GitHub Actions.

Note that our account was provisioned on Sonatype's new infrastructure, so you'll need to use https://s01.oss.sonatype.org as the URL. https://central.sonatype.org/publish/publish-gradle/#metadata-definition-and-upload has details on the new URLs to use.

Also, the sync from Sonatype to Maven Central is not enabled yet. They said "Please comment on this ticket when you've released your first component(s), so we can activate the sync to Maven Central." So we'll need to do that after we publish a pbandk release.

[garyp]

I'll try to get the PGP key created tomorrow and pull down your changes to test them out.

[JeroenMols]

@garyp I've incorporated your suggestions and this PR is ready for a new rounds of review.

Two remarks:

• I'm unavailable over the weekend, but feel free to make/push changes to this branch.
• All this code is still untested 😅 , and I'm not sure if I properly migrated everything that used to be in PublishingExtension.addMavenCentralRepository(), so please take extra care reviewing that

[garyp]

I have the PGP key generated and I've been trying to test this PR locally. But for some reason neither the signing nor publishing tasks are showing up. I'll keep poking at it...

[JeroenMols]

Is this because I skip the configuration if no credentials/signing keys are present?

pbandk/build.gradle.kts

Line 51 in 0c58dc8

if (!sonatypeApiUser.isPresent || !sonatypeApiKey.isPresent) {

[JeroenMols]

Also the publishToMavenCentralRepository task doesn't exist, I think that needs to be just publish or we should use your suggestion wrt the publications api

[garyp]

Of course I figured it out 5 minutes after writing that. I was trying to use a property file that Gradle doesn't actually read. That's what I get for trying to do this while tired yesterday 😔 I can see both the signing and publishing tasks now (I updated it to use the publishing API). I'll do some more testing later this morning and push up my changes.

[JeroenMols]

Thank you for driving this forward @garyp ! 🙏
Please let me know if I can help.

[garyp]

I realized that we can get snapshot builds more or less for free by just running the "release" workflow for all pushes to the master branch. The nexus-publish gradle plugin automatically chooses whether to publish to the OSSRH snapshot or release repository based on whether the version name includes "-SNAPSHOT".

[garyp]

@JeroenMols FYI, if you ever need to test the latest code on master, every commit to master should now publish artifacts at this maven URL.