@lemire I realized that even though the release succeeded, the new artifact wasn’t published. After a couple of fixes, I think we’re close to finishing this. However, now I’m getting the following error:

Are you sure the Maven credentials are correct? A few months ago, for simdjson-java, I had to generate a new token because OSSRH was sunset. I believe I followed these instructions: https://central.sonatype.org/pages/ossrh-eol/#publishing-to-central-portal.

Let us try again

Ok. It does something, but it is not automated. From what I understand, I still have to manually login and request publication after waiting a really long time, and then... I don't know, hope that it works somehow?

8 minutes. I am not kidding.

18 minutes.

25 minutes.

Did it fail, did it succeed?

My goal is to make it fully automated. Let’s give it a bit more time. If it doesn’t show up, I’ll investigate.

The primary reason I stopped using Maven Central is that releases could take days or weeks to appear and would sometimes be randomly dropped. It is poorly designed.

Over one hour:

My goal is to make it fully automated

Currently, it is not automated. I had to go in the system, find the artifact and ask that it'd be published.

Notice how the system lacks any kind of feedback as to what is happening.

Clearly, my credentials are correct...

I agree with you.

My motivation for adding support for Maven Central is that some organizations are restrictive about which repositories can be used in their projects. They often have an internal proxy or cache for Maven Central; and that’s it.

In simdjson-java, I haven’t had any problems so far, and I don’t need to do anything manually, so it’s definitely possible to make this work. However, I’m using Gradle there, so I can’t easily copy the configuration here.

Anyway, I will figure this out.

My motivation for adding support for Maven Central is that some organizations are restrictive about which repositories can be used in their projects. They often have an internal proxy or cache for Maven Central; and that’s it.

I agree with this.

[INFO] [INFO] Continue at https://central.sonatype.com/publishing/deployments to review and publish the deployment eb7c5be7-3fca-431b-ad4a-7131adb4064e

from Github CI indeed suggest current setup requires to complete the deployment manually.

Though, @lemire, the screenshots Sonatype process is on-going. I had to go in the system, find the artifact and ask that it'd be published. is the missing part.

I do not know njord, but my experience with maven+sonatype does not require any manual validation (through the publication may take hours to be fully completed). Though, I never fully automated it through CI. I looked through njord to enable automated publication, but it may be a lacking option.

I rely on configuration like:

	<!-- https://central.sonatype.org/publish/publish-portal-maven/#automatic-publishing -->
	<plugin>
		<groupId>org.sonatype.central</groupId>
		<artifactId>central-publishing-maven-plugin</artifactId>
		<version>0.9.0</version>
		<extensions>true</extensions>
		<configuration>
			<publishingServerId>central</publishingServerId>
			<autoPublish>true</autoPublish>
			<!-- `published` state can take hours to be reached-->
			<waitUntil>validated</waitUntil>
		</configuration>
	</plugin>

(https://github.com/solven-eu/adhoc/blob/master/pom.xml#L685-L696).

Three hours:

Not an indication of what is happening.

It works now, so I have entered some comments in a related RoaringBitmap issue: RoaringBitmap/RoaringBitmap#749

Did you need to click anything in Maven Central?

@piotrrzysko Not with the latest setup.