This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-04
Channels
- # beginners (90)
- # boot (5)
- # cider (89)
- # cljsrn (27)
- # clojure (33)
- # clojure-dev (2)
- # clojure-italy (3)
- # clojure-spec (35)
- # clojure-uk (17)
- # clojurescript (93)
- # code-reviews (1)
- # datascript (2)
- # datomic (14)
- # defnpodcast (6)
- # emacs (11)
- # figwheel (8)
- # figwheel-main (6)
- # hyperfiddle (14)
- # jobs-rus (1)
- # nrepl (3)
- # off-topic (13)
- # onyx (6)
- # reagent (6)
- # reitit (4)
- # shadow-cljs (110)
- # spacemacs (1)
- # tools-deps (10)
- # vim (17)
I don’t understand what you’re asking
@alexmiller the primary reason I’ve been using boot is for dependency management. From what I gather there is a built-in solution in Clojure for this exact purpose? (i.e. specify and download dependencies)
@hmaurer If all you're using Boot for is dependencies -- for a REPL or running code -- then clj
will do what you need.
If you want to build JAR files, there are several options. depstar and juxt/pack both work with just deps.edn/clj. Or you could use boot-tools-deps
to leverage deps.edn/clj but let Boot build artifacts from that.
(we've had our deps in external EDN files with Boot for years so we're looking at switching over to deps.edn/clj for a lot of day-to-day stuff)