Hey @U7KD4HQ1W, thanks for giving it a go 🙂 That sounds like a connection error, potentially?

Recent pom and jar artifacts are present there https://s01.oss.sonatype.org/content/repositories/snapshots/com/xtdb/xtdb-api/2.0.0-SNAPSHOT/ so I agree it sounds like a connectivity issue and could be retried? (maybe clean any com/xtdb stuff out of your local ~/.m2/repository to force a refetch?)

Hi both. There were some com/xtdb entries in my local repository, I deleted and retried maven, it just recreated them. Also yesterday and today I tried in 2 separate locations and on 2 separate computers so it looks like it must be a connection problem. @U04V70XH6 if you put that URL into a web browser does it show anything to you? For me I just get "An error occurred during a connection to http://s01.oss.sonatype.org. PR_END_OF_FILE_ERROR"

I can ping the http://s01.oss.sonatype.org though

Works for me (tm):

Are you behind a corporate firewall perhaps?

Currently at home! I am in the UK. Could it be some kind of certificate error? I'm not an expert at that kind of thing

Me neither. But those errors do indicate some sort of SSL-related problem. What mvn version are you using and what O/S etc?

mvn 3.9.1, macos (I also tried on Win 11)

I see some internet reports of people getting those PR_... errors if their ISP has blocked the site. Maybe it's that. I will investigate.

Hmm yes I can browse to that site on my phone if I turn wifi off & use mobile data - must be being blocked by my ISP, do you agree?

Bizarre... Who is your ISP?

Alright I added the site to the allowed list at my ISP and now I can browse to that site. Weird though it was also blocked in the other location because I know they use a different provider. Anyway fingers crossed it'll be OK now

Thanks!

Failure... and then success... I also needed to add clojars to the repositories in my pom.xml - maybe @U050V1N74 you could add that to your instructions on the site?

whew 😅

ah, yep. we're https://github.com/xtdb/xtdb/issues/3161 to remove the dependency on Clojars in the near future but should include the workaround in the docs for now