This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-17
Channels
- # bangalore-clj (2)
- # beginners (202)
- # boot (18)
- # cljs-dev (8)
- # cljsjs (7)
- # cljsrn (4)
- # clojars (2)
- # clojure (401)
- # clojure-boston (2)
- # clojure-dusseldorf (1)
- # clojure-gamedev (36)
- # clojure-greece (2)
- # clojure-italy (1)
- # clojure-russia (16)
- # clojure-spec (27)
- # clojure-uk (7)
- # clojurescript (68)
- # core-async (16)
- # cursive (25)
- # datascript (1)
- # datomic (34)
- # funcool (1)
- # hoplon (1)
- # interop (1)
- # klipse (1)
- # leiningen (2)
- # lumo (75)
- # off-topic (17)
- # om-next (2)
- # onyx (66)
- # re-frame (18)
- # reagent (2)
- # ring-swagger (11)
- # spacemacs (1)
- # specter (1)
- # timbre (3)
- # untangled (48)
- # yada (7)
the task option dsl wiki page says that the long-name option names are available in the body of the task. but as soon as there's something like (boot.pod/with-pod (boot.pod/make-pod (get-env)) &body)
that doesn't seem to be true anymore.
is there a way to check for newer versions of my build.boot :dependencies?
lots of old deps, omg
thanks!! 🙂
so things... it's been, you know, stuff and junk
you too!
for convenience, i have this in my profile.boot:
(set-env! :dependencies '[[boot-deps "0.1.6"]])
(require '[boot-deps :refer (ancient)])
then regardless of what project i'm in, i can run boot ancient
and it will tell me which dependencies have newer versions available
nice! thanks ❤️
boot/new
0.5.2 was just released with improvements for Boot/Leiningen template handling: the error messages when a template cannot be found/loaded have been improved; the README explains the workflow for developing/testing a new template. Thanks to @mobileink for that!