-
Notifications
You must be signed in to change notification settings - Fork 56
launchdarkly-java-server-sdk 5.2.2 jar is not in maven central #223
Comments
Hi @chenrui333, Maven Central has had some incidents over the past day plus which introduced a lot of service latency. Here is today's incident which elongated our SDK release process this afternoon. I verified that 5.2.2 is in Maven Central per https://repo1.maven.org/maven2/com/launchdarkly/launchdarkly-java-server-sdk/5.2.2/ even if the Maven Repository site says otherwise. I also verified as much in a local build. Hopefully Maven Repository will catch up soon and Maven Central's issues will be behind them. I'll leave this ticket open until 5.2.2 shows up on the linked page. Cheers, |
@bwoskow-ld that totally makes sense, thanks!! :) |
It looks like the 5.2.2 version propagated out to Maven Central's mirrors and ancillary services some time over the past few days. I'm going to go ahead and close this issue. |
Thank you! Gonna retry on my end. :) |
(#3) simplify store status implementation to not use optional interface
👋 looks like the jar is not in the maven central yet, just FYI.
The text was updated successfully, but these errors were encountered: