bindings java: publish to maven repo fails

[danbev]

The bindings-java job failed in this run. This task should take a look at why this happened and address the issue. The specific error is:

* What went wrong:
Execution failed for task ':publishMavenJavaPublicationToMavenRepository'.
> Failed to publish publication 'mavenJava' to repository 'maven'
   > Could not PUT 'https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/io/github/***/whispercpp/1.4.0/whispercpp-1.4.0.jar'. Received status code 401 from server: Content access is protected by token

Could this perhaps be that Sonatype has moved to a User Token Authentication during the period this CI job was disabled? In that case perhaps we need to generate a User Token and update the JIRA_USER and JIRA_PASS github secrets. To do this I think we need to login to the account in https://s01.oss.sonatype.org/#welcome

Another possible cause could perhaps be the moving of the the repo to ggml-org. We should probably update group to io.github.ggml-org. I think this requires that we claim this new group id with Sonatype.

[danbev]

@ggerganov Do you have any ideas about this and what the issue might be? I can't check the github secrets and I don't have access to the Sonatype console to figure this out so I'm a little stuck at the moment.

[ggerganov]

Not sure. I think we set this up in https://github.com/ggml-org/whisper.cpp/pull/944.

But visiting some of the links from that discussion, it seems this repository is being decommissioned: https://central.sonatype.org/faq/what-happened-to-issues-sonatype-org/

Probably it's best to disable this publish workflow.

[danbev]

Not sure. I think we set this up in #944.

But visiting some of the links from that discussion, it seems this repository is being decommissioned: https://central.sonatype.org/faq/what-happened-to-issues-sonatype-org/

Probably it's best to disable this publish workflow.

Thanks, I'll disable it for now and try to take a closer look at those links.

[nobeh]

@danbev @ggerganov 👋🏻 Thanks for creating and maintaining such great piece of technology.

I am Java developer by craft. I'd like to contribute to this issue to make it more seamless to use the Java bindings from the future releases.

The discussion mentions

• Move to Maven groupId io.github.ggm-org
• Do you expect the above to happen at POM level or only Sonatype?
• Who could help to claim the above Group ID at Sonatype to start testing with this?

Thanks