we are doing like the above, I have also a deps.edn only project but having lein makes it easy for colleagues to use Cursive, which still has some quirks with deps.edn

@richiardiandrea It does? I’d like to hear about them.

👋 I asked this yesterday in off-topic, wondering what you think about it https://clojurians.slack.com/archives/C03RZGPG3/p1547483045535400 One thing I would fear if people widely adopted "SHAs for every dependency" is that two different libraries (let's call them A and B) could independently declare a dependency on C, but at different SHAs. Is that a scenario that tools.deps can gracefully handle?

yes

well depends what part you’re asking about

if you declare two sha’s in the transitive dep tree, it will use the newer one

(same as we do for Maven artifacts)

So in this library I’m hoping to help out with, I’ve moved the dependencies from project.clj to deps.edn and added the plugin lein-tools-deps to project.clj. lein deps seems to work just fine, but when I run lein test I get:

$ lein test
Error: Could not find or load main class clojure.main
Caused by: java.lang.ClassNotFoundException: clojure.main
Tests failed.

seems like your tests are not picking up the dependencies

I wonder if your lein-tools-deps plugin isn't working in the test profile

Hmm, OK, I’ll look into that — thanks!

Aha, I needed to add :middleware and :lein-tools-deps/config to project.clj — as explained clearly in the docs of lein-tools-deps! (docs ftw)

@aviflax I had that same problem with Cursive and the only thing I found to get around it was to downgrade lein-tools-deps to "0.4.1"

Have you tried adding those keys to your project.clj ?

I have a codebase that I’ve instrumented with tools-deps and can run via

clj -m something.main <args>