This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-14
Channels
- # announcements (2)
- # aws (12)
- # aws-lambda (5)
- # beginners (42)
- # calva (56)
- # cider (16)
- # clj-kondo (1)
- # cljs-dev (45)
- # cljsjs (1)
- # cljsrn (25)
- # clojure (171)
- # clojure-europe (3)
- # clojure-italy (16)
- # clojure-losangeles (2)
- # clojure-nl (49)
- # clojure-spec (2)
- # clojure-sweden (3)
- # clojure-uk (11)
- # clojurescript (84)
- # component (11)
- # core-async (12)
- # core-logic (2)
- # cursive (8)
- # datomic (41)
- # events (2)
- # fulcro (48)
- # graalvm (1)
- # graphql (1)
- # hoplon (12)
- # jackdaw (1)
- # jobs (1)
- # jobs-discuss (45)
- # joker (5)
- # keechma (10)
- # nyc (3)
- # off-topic (14)
- # pathom (16)
- # qa (1)
- # re-frame (22)
- # reagent (12)
- # reitit (4)
- # remote-jobs (1)
- # shadow-cljs (40)
- # spacemacs (3)
- # timbre (3)
- # tools-deps (29)
Yes - the old version of jetty aws-api uses is not compatible with the latest version of jetty.
I explicitly updated http-client to the latest and it fixes the conflict. Seems like aws-api should update to the latest as well.
another way to handle is to explicitly depend on latest Jetty, I think that http-client is compatible with it
cljc and ClojureScript would be most interesting thing to offer, thinking about React Native
Using a http client that doesn’t use jetty (i.e. http-kit) would be great. Ring pulls in 9.4.
replied to a thread:we're considering a model for BYOHttpClient too
cljc and ClojureScript would be most interesting thing to offer, thinking about React Native