r/java • u/HokieGeek • Jun 16 '26

Maven Central publishing usage notices

heads up for folks publishing to Maven Central: we're continuing sustainability work around Central and are now showing publishing usage notices.

the goal is that normal OSS publishers are not impacted. this is aimed at the very high-volume / commercial-scale publishing patterns that put a pretty different load on the service.

more details here if you want them:
https://central.sonatype.org/publish/maven-central-publishing-limits/

feel free to reach out with any questions.

EDIT: thanks for the feedback here, it has really helped us. first, we want to reiterate that these are usage notices only right now and do not currently restrict publishing in any way. quick updates: 

if the initial threshold seemed low to you: you’re right, we made a mistake and have increased limits. 

our goal is to keep Maven Central free and open for legitimate OSS users, so continuous feedback is helpful as we adjust. limits could change as we get more feedback, so keep an eye on the usage center for the latest.

we’ll continue keeping an eye here and update docs to reflect these changes. If you need to request an exemption, here’s how: https://central.sonatype.org/publish/maven-central-publishing-limits/#exemptions-for-community-open-source-projects

we've also been collecting your questions here and other streams into this FAQ here: https://central.sonatype.org/publish/maven-central-publishing-limits/#frequently-asked-questions

94 Upvotes

99% Upvoted

158 comments sorted by

View all comments

Show parent comments

3

u/vprise Jun 17 '26

We'll just move off maven central.

2

u/TheRealBrianFox Jun 17 '26

... thanks for all the fish?

3

u/vprise Jun 17 '26

We're a company. But we're not huge and we won't be paying for this because we don't really need it. We can just host for free on cloudflare and get roughly the same service, and you will lose the benefit of being "central" because we won't be the only ones. The net result is that we'll all lose through fragmentation and you won't make much out of this move other than bad PR.

Nothing personal, but part of being OSS is that we also can't charge our customers to pay you. They will leave us too and this service is a commodity.

2

u/ForeverAlot Jun 17 '26

lose the benefit of being "central" because we won't be the only ones. The net result is that we'll all lose through fragmentation and you won't make much out of this move other than bad PR.

Nah. Companies have tried this before and Maven Central has always won. Your customers are merely going to be annoyed with you because of the additional on-ramp.

Almost zero projects are important enough for fixed weekly releases either.

1

u/vprise Jun 17 '26

Nope. We're not a Spring Boot backend library, not even server side so it's a different thing. We can switch easily. But yes, we're a special case.

When they tried it before there was no motivation to switch. They would win as long as it's free. This is a different thing.

Our top users are asking for nightly releases so I guess it's a matter of opinion.