Maven Central is borderline unusable

Summary

For a few months now we (the Eclipse Dataspace Components project) have started publishing our Snapshot builds to Maven Central rather than of OSSRH/Sonatype.

Unfortunately, that move has turned out to be less than ideal, because we are experiencing lots of problems with Maven Central Snapshots to a point where it becomes unusable.

At the time of writing we are seeing lots of random HTTP 429 errors (see here) as well as when resolving artifacts from MavenCentral (no link, happens locally).

We presume this has to do with the fact that we are publishing a high number (300-400) of artifacts, but it was never a problem for OSSRH.

In addition, we have noticed that it takes extremely long for snapshot builds to become available on Maven Central, around 2-3 hours, occasionally more. For comparison, with OSSRH this was almost immediate.

TL;DR

We are asking for guidance on how to proceed - the current situation is becoming increasingly difficult for us. We know that some projects have project-specific artifact proxies that are synced to MavenCentral occasionally, maybe that is an idea worth exploring...

Steps to reproduce

no deterministic reproduction

What is the current bug behavior?

random HTTP 429 errors, extremely long wait times for artifacts to become available

What is the expected correct behavior?

no errors, reasonable wait times

Relevant logs and/or screenshots

e.g. IdentityHub Nightly Build, Connector Snapshot build, many others

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

This is impacting our ability to develop our projects, because we often cannot merge PRs in one project, because that depends on a Snapshot of another project and so on.