5.13.4 not available in Maven Central

[kwin]

Version

5.13.4

Operating System

MacOS

Bug description

Maven central does not provide the most recent 5.x version: https://repo.maven.apache.org/maven2/org/eclipse/jgit/org.eclipse.jgit/

Actual behavior

Release for tag/commit 85c14b4 is missing

Expected behavior

All releases should be provided on Maven Central as it is the de-facto standard for Java libraries.

Relevant log output

Other information

No response

[tomaswolf]

It should be there soon. C.f. https://eclipse.gerrithub.io/c/eclipse-jgit/jgit/+/1218789/comments/0464ed5d_ad0ccc3b .

[msohn]

I have to find time to adapt the deployment to maven central to the new process, the old one (OSSRH) was shutdown end of June.
Until that happened you can find 5.13.4 on the Eclipse Maven repo under https://repo.eclipse.org/content/groups/releases/org/eclipse/jgit/.

AFAIU apart from migrating permissions from the old to the new site we can either use the Sonatype maven plugin
https://central.sonatype.org/publish/publish-portal-maven/
or
https://maveniverse.eu/docs/njord/
to publish releases via the Maven Central Portal on maven central.

I guess I should start by filing an issue under https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5854 to get assistance from the release engineers at the Eclipse Foundation.

[kwin]

I recommend using https://github.com/maveniverse/njord (see also https://github.com/apache/maven-studies/tree/deploy for an opinionated evaluation)

[msohn]

Do you have experience using njord and can point me to some examples ?

So far JGit CI builds are deployed to repo.eclipse.org and we have some scripts to download releases from repo.eclipse.org
and deploy them to maven central. I would prefer a solution where a release CI job downloads a release from repo.eclipse.org and then deploys it to maven central.

[kwin]

It is for example used in https://github.com/jline/jline3/blob/master/.github/workflows/release.yml or https://github.com/orbinson/workflows/blob/main/.github/workflows/maven-release.yml. However both assume that you publish the artifacts you build. But you can use it also standalone, the idea would be then to a

1. execute https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html to publish an artifact to the local staging area/store (for each relevant artifact)
2. execute https://maveniverse.eu/docs/njord/plugin-documentation/publish-mojo.html to publish all artifacts in the previously populated store to the Central Portal

[msohn]

I filed https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/6589 to get help from Eclipse release engineers to migrate the deployment process to Maven Central from OSSRH to the Maven Central Portal.

[mhoffrog]

@msohn A migration from former nexus-staging-maven-plugin to central-publishing-maven-plugin can be looked up here Migrate to Sonatype publishing via central-publishing-maven-plugin

Since Sonatype is currently maintaining central-publishing-maven-plugin in a closed repo, source code and few enhancements to the central-publishing-maven-plugin can be found here central-publishing-maven-plugin - full documentation available there as well.

[kwin]

@msohn Would it be possible to publish this version manually as outlined in https://central.sonatype.org/publish/publish-portal-upload/ until the automation scripts are in place?