This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-14
Channels
- # announcements (3)
- # babashka-sci-dev (22)
- # beginners (6)
- # calva (36)
- # cljsrn (1)
- # clojure (59)
- # clojure-europe (31)
- # clojure-france (3)
- # clojure-gamedev (1)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-uk (4)
- # clojurescript (6)
- # conjure (1)
- # cursive (11)
- # data-oriented-programming (1)
- # datahike (2)
- # docker (8)
- # duct (4)
- # emacs (1)
- # figwheel-main (5)
- # kaocha (1)
- # leiningen (8)
- # lsp (64)
- # malli (10)
- # membrane (5)
- # nrepl (11)
- # off-topic (5)
- # portal (6)
- # quil (9)
- # reagent (62)
- # reitit (15)
- # releases (3)
- # ring-swagger (2)
- # shadow-cljs (36)
- # specter (2)
- # tools-deps (21)
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?
yes, we really want prep to be an explicit independent action, rather than an implicit thing
yes, it's running arbitrary third party code on your machine
for libraries, requiring prep should often drive you to artifacts instead
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
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
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?
yeah, there's no way to supply that externally
is it lein project?