This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-05
Channels
- # aleph (190)
- # bangalore-clj (4)
- # beginners (31)
- # boot (127)
- # braid-chat (2)
- # cider (2)
- # cljs-dev (79)
- # cljsrn (7)
- # clojure (81)
- # clojure-dev (1)
- # clojure-greece (40)
- # clojure-italy (3)
- # clojure-korea (8)
- # clojure-new-zealand (5)
- # clojure-russia (5)
- # clojure-spec (87)
- # clojure-uk (13)
- # clojurescript (50)
- # cloverage (10)
- # component (4)
- # core-async (37)
- # cursive (26)
- # datascript (20)
- # datomic (29)
- # editors (2)
- # emacs (12)
- # hoplon (63)
- # jobs (2)
- # lein-figwheel (1)
- # leiningen (17)
- # liberator (2)
- # off-topic (19)
- # om (31)
- # onyx (9)
- # pedestal (4)
- # proton (1)
- # re-frame (22)
- # reagent (13)
- # ring (1)
- # ring-swagger (9)
- # spacemacs (5)
- # specter (4)
- # untangled (24)
- # vim (29)
I am also working on AWS related plugin (deploying AWS Lambda with API Gateway support) and ran into same issue with old Jackson version
is there a way to exclude
that dependency from cheshire in the project.clj, and manually add an updated version of jackson
?
Latest working version of AWS SDK is "1.10.77 which does not yet require newer version of Jackson. I managed to cope with that for now
@mhjort ah, I forgot about Leiningen's version of Jackson, that makes total sense now
It would be nice if we could strip leiningen into a core tool which has no dependencies (except clojure) and delivers what I would call "headless" CI build capabilities. Then additional capabilities could be layered on.
So where we have collisions on library versions between plugins you could take a decision of what's important for a given task. No clue how much effort that would be or if it is enough benefit
this way you can pretty much strip bloated project.clj to a bare-bone version, even replace dependencies
The issue with the aws-sdk and jackson is that leiningen is an uberjar, and you can’t change any dependencies of leiningen itself