What does “for a jar” mean? Is this in tools.build context?

yep, in tools.build

Is this a top level dep or a dependency?

top-level

If top, you could I think add an :extra {the/lib nil} in the basis opts

I’ll try this, thanks!

Or if modifying the basis after, the critical part is the :libs and you could just remove the lib from that map

like this?

(b/create-basis {:project "deps.edn" :extra {'io.github.nextjournal/dejavu nil}})

Yeah

still seeing a warning

clj -T:build jar
Producing jar: target/clerk-0.12.707.jar
Skipping coordinate: {:git/sha 31bdc12d78d3a8f48cbd6c3df5b8c79ca88df4f1, :git/url , :deps/manifest :deps, :deps/root /Users/mk/.gitlibs/libs/io.github.nextjournal/dejavu/31bdc12d78d3a8f48cbd6c3df5b8c79ca88df4f1, :parents #{[]}, :paths [/Users/mk/.gitlibs/libs/io.github.nextjournal/dejavu/31bdc12d78d3a8f48cbd6c3df5b8c79ca88df4f1/src]}

Should it be {:extra {:deps ...}}?

Oh, yes

We tried that and it says: expected map, got nil :)

yeah getting `Bad coordinate for library io.github.nextjournal/dejavu, expected map: nil

(def basis (-> (b/create-basis {:project "deps.edn"})
               (update :libs dissoc 'io.github.nextjournal/dejavu)))

dissocing from libs seems to work..

that seems to do it

yep, warning is gone, thanks!

Deps is really a compositional model so excluding things is a lot harder than including them. I thought I had something for the above in there but I guess not. I assume this isnt a dep that could optionally be included rather than excluded?

in that case I want to have it be there when consumed at as git dep but leave it out when I build the jar

This is a dependency that does some stuff at startup when in local dev or as a git dep, but as a mvn jar we would like to not use it since we can pre-compute what this lib is doing and also exclude the deps

Gotcha

Well I’ll think about better ways to do that