-
Notifications
You must be signed in to change notification settings - Fork 34
Use AWS SDK, rather than CLI #84
base: master
Are you sure you want to change the base?
Conversation
@moea cool, will finish something and will give it a spin. Thx for the info. |
Simple
|
@zrzka Does lein version show 2.7.2-SNAPSHOT, and/or do you have anything in your profile which might be causing this? That's the same error you'd get with an earlier version of leiningen. |
Nothing special in project.clj. Pretty standard stuff. |
@zrzka There is an old version of Jackson on the lein classpath, from either another plugin in your project.clj or leiningen profile. I'm not sure that much can be done about this in the general case, aside from radical approaches, like spawning another jvm with an adjusted classpath. |
@moea hmm, is this worth to tweak it to make it working instead of simple |
@zrzka If it's a choice between spawning a jvm or sticking with awscli - then, definitely awscli - I was just hoping that it'd be plain sailing after leiningen releases 2.7.2 (which removes the old, unused jackson). |
@moea here's a list of packages that they do require jackson ... removed .m2/repositories and installed all deps again just for one project with 0.7.0-SNAPSHOT plugin
... cheshire required in many packages ...
|
@zrzka Thanks. cheshire 5.2.0 is pretty old - overriding the dependency w/ cheshire 5.7.x would probably fix that issue. That said, I think there's a difference between packages on the project classpath (direct and transitive |
@zrzka This is published as 0.7.0-SNAPSHOT. Note that it requires leiningen 2.7.2-SNAPSHOT - which is awkward enough to install that release will have to wait until 2.7.2 - unless there's some way to override Leiningen's (unused) Jackson dependency, so it doesn't conflict with the AWS SDK's - but I don't think there is, because of differences between plugins and projects.
I'll leave this open until then, let me know if you encounter any issues - it should operate identically to the existing project.