Fork me on GitHub
Alex Miller (Clojure team)00:03:10

I do have an option like that buried in the code, don't remember if there's a path to get it there from the cli (or if I want that to even be available)


Another option could be to pass :prep via the CLI, e.g. -Sprep so you will always have the prepped classpath. Is there anything against doing this?

Alex Miller (Clojure team)16:03:12

yes, we really want prep to be an explicit independent action, rather than an implicit thing


because missiles can be launched during prep?

Alex Miller (Clojure team)16:03:06

yes, it's running arbitrary third party code on your machine


and without prep, you have a potentially incomplete classpath, right?


as in, missing target/classes in git libs, for example

Alex Miller (Clojure team)16:03:43

for libraries, requiring prep should often drive you to artifacts instead

Alex Miller (Clojure team)16:03:54

but it can be useful for local dev, or other situations


yeah, preview / dev versions etc, and then publish as artifact when ready to release

Alex Miller (Clojure team)16:03:45

like we were able to do with transit-java recently - made it available as a git lib on a branch, which required prep, and then released as an artifact once tested


makes sense


There is no way to use a non-deps.edn project as a deps.edn project when it has a non-standard source folder src/clj right?


Else I could have used :deps/manifest :deps

Alex Miller (Clojure team)19:03:01

yeah, there's no way to supply that externally


open an issue for them to keep a lein pom reasonably up to date?


it's not so urgent, I'm keeping a fork around with a deps.edn in it

👍 1

until the next release