Adapt Maven Central release to Token based credentials

[pazkooda]

Due to e-mail send from Maven Central we should update our credentials to be able to publish artifacts to Central Repository:

from: The Central Team central+announce@sonatype.com reply-to: central-publishers@sonatype.com to: ... date: 11 Jun 2024, 18:00 subject: Maven Central account migration

Dear Maven Central publisher,

We are making changes to the OSSRH authentication backend. For most users this should be a transparent process, and you should be able to continue to use your existing username and password to connect the Nexus UI. In case you need to update your password, please follow our documentation.

To configure a publisher’s plugin authentication you would need to update your plugin settings to use a user token instead of the Nexus UI username and password login.

For more information about publishing to legacy OSSRH please consult our documentation at https://central.sonatype.org/register/legacy/

Thank you, The Central Team

If I correctly understood simple change of secrets.NEXUS_PASSWORD to secrets.NEXUS_TOKEN (to be generated and set in GH) in this line: https://github.com/TietoEVRY/quarkus-resteasy-problem/blob/358f9a7491b27bec4908b6db0d1cb577b8614c8c/.github/workflows/publish.yml#L24 should do the job.

[lwitkowski]

Seems to be working fine for publishing snapshot:

I had to extend the gpg signature key as well, which turned out to be expired 2 months ago. Thanks @pazkooda