Live data from Hacker News

Migrating old artifacts from JCenter to MavenCentral

marcogomiero.com

21–22 of 22 posts

Re: Migrating old artifacts from JCenter to MavenCentral

#21
post #19

Earlier quoted context omitted.

> Unless they look forward to manually approving gazillions of requests from stranded JCenter users in the next weeks. Maybe business is that good that they don't care about the overhead. Getting approved for a groupId took me literally 2 minutes. It's really not that complicated. Not sure yet about the process for actually getting releases approved, I'll see about that tomorrow.

Took me about half a week last time I tried this. That's from signing up to getting all the approvals needed and finally getting my jar out via maven central. I imagine they may have improved their processes a bit since then but as far as I know it still involves creating tickets in their issue tracker and a human doing stuff with it.

My package is now released. 24 minutes to go from "opening the ticket" to it being approved, and another 14 minutes to go from "first publish to staging" to it being publicly available on repo1.maven.org.

Sure, a human is still involved, but it’s definitely faster than anything else in the release process.

If there’d be something to improve, it’d be (a) having a built-in publish plugin in gradle with a publish.json that easily defines the variables and adds a super simple way to publish, and (b) automating the TXT verification akin to google-site-verification (plus potentially github oauth login to validate com.github namespaces).

Re: Migrating old artifacts from JCenter to MavenCentral

#22

I wish Java would move to more distributed artifact storage. Just specify URL and let your build tool download library there. Why does it have to be some kind of central storage? It's not like they perform some curating or static analysis or something like that.

Actually we do validate several aspects of things being published to Central and always have. There have been many other repos that have come and gone over the years, many of them without the same standards and it ultimately creates a federated tragedy of the commons. More about the history here https://blog.sonatype.com/why-namespacing-matters-in-public-...
Post reply on HN