Fork me on GitHub
#leiningen
<
2016-10-05
>
mhjort16:10:24

I am also working on AWS related plugin (deploying AWS Lambda with API Gateway support) and ran into same issue with old Jackson version

roberto17:10:02

is there a way to exclude that dependency from cheshire in the project.clj, and manually add an updated version of jackson?

roberto17:10:09

I would think that should work with exclusions

roberto17:10:33

it is a pain, but it is probably a temporary workaround?

mhjort17:10:27

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

mhjort17:10:35

1.11.x requires new Jackson

danielcompton19:10:10

@mhjort ah, I forgot about Leiningen's version of Jackson, that makes total sense now

nfisher20:10:36

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.

nfisher20:10:34

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

nfisher20:10:50

To justify the effort

darwin21:10:48

@nfisher are you aware of

darwin21:10:05

^:replacewhen using lein :profiles ?

darwin21:10:36

this way you can pretty much strip bloated project.clj to a bare-bone version, even replace dependencies

csm22:10:28

The issue with the aws-sdk and jackson is that leiningen is an uberjar, and you can’t change any dependencies of leiningen itself

nfisher22:10:52

@darwin: am now thanks but as @csm mentioned when building plugins it would be nice to eliminate dependencies in the core build tool and then enable capabilities like nrepl in development, clojar deployment in CI, etc.

nfisher22:10:35

Don't think technomancy is on here so might raise it as an issue on the GH page.