Automate publishing of DefectDojo Java Client release to maven central

[Weltraumschaf]

• https://docs.gradle.org/current/userguide/github-actions.html
• https://github.com/gradle/gradle-build-action

[J12934]

Mhh? It's automated: https://github.com/secureCodeBox/defectdojo-client-java/blob/main/.github/workflows/publish.yml
Getting automatically published when a github release is created. @Weltraumschaf

[Weltraumschaf]

Build is automated, but there is no such release in Maven Central.

[J12934]

@Weltraumschaf should publish to maven central when the release doesn't contain snapshot
https://github.com/secureCodeBox/defectdojo-client-java/blob/main/build.gradle#L81

[Weltraumschaf]

Long time ago (~4 years) @rseedorff requested access to Maven Central. They said we should release some SNAPSHOT versions before they grant us access to the public repo. Now we should hook up this process.

[Weltraumschaf]

Found the Sonatype OSSRH issue:

Looks like everything is prepared to perform a release. @rseedorff do you have the GPG key to sign the jars? Do you have your Jira Account working and can login here?

[Weltraumschaf]

We also need to meet some requirements:

• Supply Javadoc and Sources
• Provide Files Checksums
• Sign Files with GPG/PGP
• Sufficient Metadata

Documentation how to do this with Gradle.

[Weltraumschaf]

I've raised an comment in the OSSRH issue and asked how to add more maintainers.

[Weltraumschaf]

@J12934 and me now have publish rights to our Sonatype staging repo. Now we can test a first release.

[Weltraumschaf]

Gradle documentaton from sonatype