Hey guys :wave: just wondering if some of you succ...
# library-development
a
Hey guys 👋 just wondering if some of you succeeded in migrated to new Maven Central API. For me package upload is taking x8 times initial time compared to s01 server 🐌🐌🐌 taking me 38 min to release 😕
j
It happened to me the first time (same as you, from almost being instantaneous to take 10 minutes). But the next times it was faster, but I haven’t benchmarked the difference, tbh.
a
still taking really long time to go yes 😕
I'm fighting with closing repo also getting some 400s errors
v
You could try whether the old API works faster on the new infrastructure. You can use the same publshing as before with just a new URL. https://central.sonatype.org/publish/publish-portal-ossrh-staging-api/
m
closing repo
You guys are closing repos? Where is that option?
This is what it looks from my end, I can "publish" or "drop" but no "close"
v
Hm, maybe that's the point. Maybe he is using the OSSRH Staging API I linked to. Because iirc you then still need to close the repo and others also reported the OSSRH Staging API is slower than the new API?
1
m
Looks like it. But where is even the UI matching
<https://ossrh-staging-api.central.sonatype.com/service/local/staging/deploy/maven2/>
?
I assume both https://s01.oss.sonatype.org/ and https://oss.sonatype.org/ are gone now so it can't be it?
v
Iirc you have to do the close programmatically, not via some UI
👍 1
m
Gotcha 👍
a
with publish-plugin, I can run "publishToSonatype" and the "closeAndReleaseSonatypeReleaseStagingRepository" ... https://github.com/gradle-nexus/publish-plugin/?tab=readme-ov-file#publishing-to-maven-central-via-sonatype-central I've changed url on config. But I get error 400 on close. But everything is deployed apparently 🤷
j
Nexus plugin is not working very well with the new infrastructure, it was missing artifacts… you should migrate to other plugin like the one from @mbonnin or @vanniktech
1
m
> But everything is deployed apparently That picture shows your deployment as "validated" (closed in the old terminology) but not "published" yet. If you want it to be published, you need to hit the "publish" button ("release" in the old terminology)
a
That picture shows your deployment as "validated" (closed in the old terminology) but not "published" yet. If you want it to be published, you need to hit the "publish" button
yes build my gradle command says error 400 ^^
I'm not super confident here 😄
m
Ah yea.. well, it's the "compat" mode.
I think it should work fine but I would still migrate to the new infrastructure as @Javier said
j
That is the problem, I uploaded multiple artifacts that were validated but it was missing tons of them. The total number of artifacts to were 49, and only 23 was uploaded and validated…
blob open mouth 1
So I was publishing them but after checking manually the index I caught the issue, no way to see it locally as Gradle was even passing a lot of times.
v
@Vampire did you changed for https://central.sonatype.org/publish/publish-portal-ossrh-staging-api/ url ?
Not yet, didn't release since the decommission. Your problem is probably that you do the
...CloseAndRelease...
but need to use only the
close
without
release
.
r
While migrating my large project from OSSRH to new Central Portal I've tried using OSSRH Staging API but it was very poor experience. Timeouts, missing artifacts and other problems. I've finally decided to drop old configuration completely and move to new API (using nmcp gradle plugin).
🚀 2
👍 1
a
thinking the same 👍 so much errors with gradle-publish 😕
d
I publish the Immutable Arrays library using the gradle-maven-publish-plugin. You could copy my configuration: https://github.com/daniel-rusu/pods4k/tree/main The main things to look at are: • libs.versions.toml • gradle.properties • and the "publishing" module