This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-06
Channels
- # beginners (32)
- # boot (17)
- # cider (4)
- # clara (112)
- # cljs-dev (3)
- # cljsjs (2)
- # clojure (222)
- # clojure-germany (3)
- # clojure-greece (1)
- # clojure-italy (4)
- # clojure-losangeles (4)
- # clojure-russia (46)
- # clojure-spec (24)
- # clojure-uk (71)
- # clojurescript (78)
- # community-development (5)
- # component (88)
- # cursive (6)
- # datomic (7)
- # duct (5)
- # figwheel (2)
- # fulcro (21)
- # graphql (22)
- # leiningen (3)
- # luminus (9)
- # off-topic (1)
- # om (16)
- # onyx (46)
- # portkey (30)
- # re-frame (47)
- # reagent (5)
- # remote-jobs (1)
- # ring (12)
- # ring-swagger (13)
- # rum (1)
- # shadow-cljs (81)
- # spacemacs (1)
- # specter (33)
- # sql (2)
- # test-check (2)
- # vim (16)
- # yada (11)
if I update jar locally (for testing) and then in the app that I'm using that package, do I have to restart the repl or it's enough to re-evaluate (set-env! ...
?
https://github.com/boot-clj/boot/wiki/Boot-Environment#env-keys (see checkouts key)
i don't think i understand what checkouts give you over just running lein install
(or boot build-jar install
or whatever) in the project you're depending on / developing
This does it automatically
whenever you make changes
so it's like adding a watch on that project in your local maven repo, in addition to the fileset of the bigger project
yep exactly
Lein ones are source based, whereas boot ones just reinstall the JAR into your ~/.m2 and the boot watcher picks up the change
(At least i think that's what the boot one does)
NOTE: checkouts only works in the root of a project, you can’t wrap it in a task, or anything else, it won’t pickup the changes otherwise