This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-29
Channels
- # aws (6)
- # beginners (33)
- # bitcoin (2)
- # boot (22)
- # carry (2)
- # cider (5)
- # clara (21)
- # cljs-dev (115)
- # cljsrn (40)
- # clojure (161)
- # clojure-dev (73)
- # clojure-italy (38)
- # clojure-russia (88)
- # clojure-spec (123)
- # clojure-uk (58)
- # clojurescript (88)
- # core-async (26)
- # cursive (5)
- # datascript (18)
- # datomic (26)
- # hoplon (50)
- # java (2)
- # jobs (1)
- # leiningen (10)
- # lumo (1)
- # off-topic (18)
- # om (9)
- # onyx (26)
- # parinfer (13)
- # pedestal (41)
- # quil (1)
- # re-frame (27)
- # reagent (21)
- # ring-swagger (11)
- # slack-help (3)
- # spacemacs (8)
- # specter (5)
- # sql (42)
- # timbre (1)
- # uncomplicate (7)
- # untangled (3)
- # videos (1)
- # yada (26)
I don't want to disable the protection.
Can anyone offer any help working around a dependency clash in a Leiningen plugin? I’m trying to use Amazonica within a Leiningen plugin and struggling with what I believe to be a clash between the version of jacksonxml used by Leiningen and that used by Amazonica.
I thought that I could work around this by setting :eval-in-leiningen false
but I seem to have been mistaken.
I would be very grateful for any suggestions or pointers.
Yeah this is brutal
@paulbutcher leiningen on master doesn't use cheshire -> jackson anymore, so if you built and ran that version you would probably be fine
Ah - that’s good to know. This is a plugin that I’ll hopefully be releasing for others to use - do you know when this will be released (so I don’t have to tell everyone to use master)?
https://github.com/technomancy/leiningen/issues/2269 is the best info I know of
Coming before the end of the year probably, but not sure further than that
Cool. Thanks.