Hey guys, I am experiencing a big delay on for the...
# library-development
r
Hey guys, I am experiencing a big delay on for the new published artifact to be available in maven central. I usually see it there after like 30min - 1hour. This time I left it over night and it is still not there. Have you guys ever experienced this? Is there something I can do? Btw this is where I usually check if it is available: (I was hoping to see 1.5.8-beta) https://repo1.maven.org/maven2/io/github/raamcosta/compose-destinations/core/
j
You can sync before it appears there
r
I just tried in a project and I couldn’t get the new version
j
the status is not showing any outage, it is weird. I can usually sync after 5/10 min
r
found an issue on gradle slack 😛
seems like there was some issue with their sync processes
👍 1
ahh lol nevermind this was from April 6th xD
ok so I don’t know whats up
j
have you checked logs?
r
Which logs?
j
To ensure you are publishing to maven central and not snapshot repository or something so
have you moved to the new domain?
r
I mean, I haven’t changed the way I do it and I see the new version in the sonatype repository links like this: https://s01.oss.sonatype.org/content/groups/public/io/github/raamcosta/compose-destinations/core/
j
and you can't sync?
I am not at home so I can't try, in a few hours I will
r
Nope
Failed to resolve: io.github.raamcosta.compose-destinations:core:1.5.8-beta
j
I would ask in the jira ticket
or try to republish
j
Did you check the activity panel in nexus? It could sometimes block on a step/verification..
r
it’s not there anymore. I released normally and it disappeared in the end as normal.
j
Ok, then a republish or opening ticket is indeed best course of action I guess.
r
Trying to republish it now
ok as expected when releasing it says that version can’t be updated xD
or were you guys saying to also increment the version?
j
It seems something is stuck then in sync process. Best to open an issue there. And if you need it quicker, incrementing the version can possibly help depending on the sync issue causing it.
👍 1
r
any experience how long these tickets get answered?
So for the record, I opened the issue and after five hours or so, they replied and fixed it. No cause was given, so my guess is that it can just happen from time to time? 🤷 Anyway, they didn’t take too long to solve it so no harm done 🙂
👍 1