You know, with the maven central monetization esse...

# http4k

[Andrew O'Hara]

You know, with the maven central monetization essentially crippling much of OSS, I can't help but feel like a new maintstream repository will emerge. I totally get how we don't want to support the whole community on the http4k org's dime by opening the http4k repo for public use. But I wonder if it would be possible to adopt jitpack as a first-class distribution platform in the meantime.

[dave]

TBH this doesn't affect most of OSS - most OSS will fall well within the limits as set out - with the possible exception of the release limit of 7 if they have lots of different projects.

WRT JitPack, it's a non-starter inside a lot of larger companies who rely on the "security" of Maven Central and actually refuse to let engineering teams consume from anywhere else. Of course, at the same time, they are puling from NPM.. 😂

Arguably Maven is the hardest popular package manager to actually get publishing set up on (you need to own the domain), so any replacement would have to also meet that bar. I'd also be interested to see if the likes of JitPack will also take the opportunity to start monetising once they see that it's a viable alternative. I suspect that Sonatype starting to charge for consumption is also on the cards (and it's actually the wider source of abuse compared to publishing traffic)

[James Richardson]

Badically every single company out there just runs on github actions, or similar. They dont cache their dependencies, so every single build hits the upstream.
Just run against a cache. Its very easy. Use varnish orca. Its free. Or something similar.
No affiliation.

[James Richardson]

I dont know why Microsoft and Google dont run a cache for builds in their estate.