datomic

adham 2025-08-18T10:01:26.929629Z

Hey all, I'm having issues with Datomic Cloud when updating Ring, I suspect the issue is related to Jetty and I'm currently avoiding it by excluding

com.datomic/client-cloud     {:mvn/version "1.0.131"
                                      :exclusions [org.eclipse.jetty/jetty-client]}
Minimum Reproducible Example (with clj)
(add-lib 'ring/ring {:mvn/version "1.14.2"})
(add-lib 'com.datomic/client-cloud {:mvn/version "1.0.131"})

(require '[datomic.client.api :as d])
(d/client {:server-type :cloud :region "us-east-1" :system "my-system" :endpoint ""})
;; => ClassNotFoundException: org.eclipse.jetty.util.log.Log
Is the exclusion enough? and are there plans to update the client to support newer versions of Jetty? Thank you!

➕ 1
onetom 2025-08-28T06:00:53.260419Z

the logging situation is starting to get a bit out of hand as other popular libs are keeping up with the ever evolving library versions. we were also considering a ring update, because we wanted to experiment with web sockets, but noticed this jetty version conflict... in the past we also wanted to tune the jetty connection timeout, but the documentations coming up by googling refer to newer versions of jetty, than the one in datomic cloud ;(

💯 1
adham 2025-08-19T07:56:46.980799Z

Thanks Jaret! For more context this also happens with the AWS libs and now there are two exclusions

com.datomic/client-cloud  {:mvn/version "1.0.131"
                                   :exclusions [com.cognitect/http-client
                                                org.eclipse.jetty/jetty-client]}

jaret 2025-08-18T11:46:56.280579Z

> and are there plans to update the client to support newer versions of Jetty? There are plans to routinely review and upgrade dependencies where appropriate. I will confirm with the next round of dependency maintenance that we review this one.