This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-03
Channels
- # adventofcode (6)
- # bangalore-clj (1)
- # beginners (15)
- # boot (4)
- # cider (14)
- # clara (1)
- # cljs-dev (1)
- # clojure (115)
- # clojure-art (1)
- # clojure-france (1)
- # clojure-greece (1)
- # clojure-korea (9)
- # clojure-russia (1)
- # clojure-spec (62)
- # clojure-taiwan (1)
- # clojure-uk (18)
- # clojurescript (5)
- # component (1)
- # cursive (3)
- # datascript (2)
- # datomic (17)
- # devcards (2)
- # editors (4)
- # emacs (65)
- # events (2)
- # funcool (4)
- # hoplon (92)
- # jobs (6)
- # london-clojurians (1)
- # luminus (1)
- # midje (2)
- # mount (1)
- # off-topic (1)
- # onyx (51)
- # protorepl (6)
- # re-frame (116)
- # reagent (7)
- # ring (2)
- # spacemacs (2)
- # specter (4)
- # untangled (1)
- # yada (1)
It’s idiomatic in leiningen to mark tests with metadata and include or exclude sets of them using lein test
subtasks. Is there a similar idiom in boot?
Does Boot have an equivalent to Leiningen's checkouts
directory?
@aengelberg There's :checkouts
in the boot environment that you can set to a value like what you pass as :dependencies
. When a dependency in the checkouts list is updated in your ~/.m2
it will replace the old version on the classpath
@martinklepsch: that functionality doesn't sound as useful as leiningen checkouts. The goal is for another project on my file system to make its source paths available in the classpath of the parent project. Then I can clojure.tools.namespace.repl/refresh
which will pick those up.