This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-30
Channels
- # arachne (23)
- # bangalore-clj (2)
- # beginners (64)
- # boot (20)
- # cider (3)
- # clara (11)
- # cljs-dev (29)
- # cljsrn (10)
- # clojure (143)
- # clojure-brasil (4)
- # clojure-dev (22)
- # clojure-dusseldorf (3)
- # clojure-italy (26)
- # clojure-sanfrancisco (13)
- # clojure-seattle-old (2)
- # clojure-spec (15)
- # clojure-uk (27)
- # clojured (1)
- # clojurescript (52)
- # core-async (13)
- # cursive (2)
- # datomic (106)
- # fulcro (45)
- # garden (1)
- # graphql (11)
- # hoplon (98)
- # jobs (11)
- # juxt (7)
- # keechma (2)
- # leiningen (36)
- # off-topic (39)
- # parinfer (13)
- # re-frame (34)
- # reagent (5)
- # ring (1)
- # rum (4)
- # shadow-cljs (83)
- # sql (1)
- # timbre (1)
- # unrepl (49)
- # vim (1)
- # yada (42)
@seancorfield using boot-deps-tools
, how do I get boot to resolve my alias dependencies without duplicating them in my boot :dependencies
?
Realised I could slurp deps.edn and (get-in [:aliases :test :extra-deps])
to set my boot deps, but maybe there is a built-in thing for this in deps?
If you're using boot-tools-deps
you should not have :dependencies
in your build.boot
file. deps.edn
replaces that.
Then you just tell deps
which aliases you want to use. Basically you should have your project setup so you can use the clj
command line tool via deps.edn
.
@seancorfield not even build dependencies (beside boot-tools-deps
)?
I would try hard to put those in deps.edn
and use aliases.
play around with boot-tools-deps
a little, but couldn't figure out how to prevent my build dependencies from ending up in the pom.xml
(and I use boot-tools-deps
from the command-line -- I don't put in build.boot
)
Have you used :scope
?
Dependencies can have scopes, wherever they are specified: [org.clojure/clojure "RELEASE" :scope "provided"]
or [adzerk/boot-test "RELEASE" :scope "test"]
(you can use a specific version, "RELEASE"
or "LATEST"
-- the latter fetches SNAPSHOT builds)
All that said, watch out for this issue when using scope: https://github.com/seancorfield/boot-tools-deps/issues/7 -- as Alex says in that thread (and has said in #tools-deps ) you really should separate your dependencies via aliases where possible.
Realised I could slurp deps.edn and (get-in [:aliases :test :extra-deps])
to set my boot deps, but maybe there is a built-in thing for this in deps?
How do I get boot to compile git checkouts against older versions of Clojure, e.g. 1.7.0?
I'm guessing it's not possible because of the "classpath conflict warning" since Boot already runs in a given Clojure version
Specify BOOT_CLOJURE_VERSION (environment variable).
If you're using boot-tools-deps
you should not have :dependencies
in your build.boot
file. deps.edn
replaces that.
Then you just tell deps
which aliases you want to use. Basically you should have your project setup so you can use the clj
command line tool via deps.edn
.
Specify BOOT_CLOJURE_VERSION (environment variable).
It appears I need to do a better job at communicating how boot-tools-deps
is intended to be used 😄 I'll have a think about that and try expand the readme today.
The TL;DR is that it expects you to have a project setup with deps.edn
where you can already start a REPL or run code via clj
. It expects you to use aliases to keep your build / dev / test dependencies separate.