This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-17
Channels
- # admin-announcements (4)
- # boot (93)
- # cider (4)
- # cljsrn (61)
- # clojure (137)
- # clojure-austin (2)
- # clojure-brasil (2)
- # clojure-dev (11)
- # clojure-dusseldorf (10)
- # clojure-greece (245)
- # clojure-russia (37)
- # clojure-spec (60)
- # clojure-taiwan (1)
- # clojure-uk (24)
- # clojurescript (36)
- # cursive (18)
- # datomic (20)
- # emacs (20)
- # funcool (1)
- # hoplon (29)
- # jobs (1)
- # keechma (1)
- # lein-figwheel (1)
- # leiningen (1)
- # off-topic (3)
- # om (10)
- # om-next (1)
- # onyx (60)
- # other-languages (14)
- # planck (26)
- # random (3)
- # re-frame (21)
- # ring (2)
- # spacemacs (8)
- # specter (56)
- # spirituality-ethics (2)
- # uncomplicate (1)
- # untangled (68)
- # yada (3)
Hi, how to get boot version within build.boot? I thought about BOOT_VERSION but is that variable set if user did not set it up before?
I think I found solution. I will freeze boot version by setting up boot.properties file
I know there is a var in boot.core, unsure of name. Perhaps boot-version
*boot-version*
that is
Setting version with boot.properties is a good thing usually though
@alandipert: thanks
that does not work: (pod/with-eval-in @(create-pod) (require '[clojure.pprint :as pp] '[boot.core :refer :all]) (pp/pprint (get-env)))
@berrysoup: that's right, pods are completely isolated clojure runtimes
the stuff in boot.core, like set-env!
and fileset and so on are not available in pods, but you can get the pod's jvm environment via boot.pod/env
var
@berrysoup: this might help: https://github.com/boot-clj/boot/tree/master/doc
@micha: thanks a lot. I found boot.pod/get-classpath and I found that pod was built correct 🙂
A weirder question, is there any way to make Boot consider new snapshot versions of deps in a script?
I noticed that lein deploy adds a lot of nifty stuff as snapshot version, and I figure that this could be useful to avoid having to update the version of my (private) dep in my boot script every time I run it.
(using version ranges in dependencies of a library you distribute via Maven is greatly frowned upon, but for an application it's fine)
Hmm. Trying that, but it doesn't seem to pull the latest dependency for some reason. Specifying the version of it manually does work, however.
0.1.0-20160617.165455-1
is the old version, 0.1.0-20160617.171241-2
is the new version.
I'm just using this for hobby projects, mind, I'm not that lazy about versioning real projects.
The odd thing is, the new version of the dep is already in my Maven cache because I already manually referred to it.
And, hey, my website's https://pounc.es/ ...
Also, @micha, you need to remove thinkminimo [dot] com from your projects' pages on GitHub...
That's just the first redirect, JS on the page will redirect you further to possibly malicious content.
Turns out that Chrome supports push notifications now, which work just like smartphone push notifications work.
Yep. And if you are a naive user and click "Allow", then you're subscribed to what I presume to be malicious push notifications. It's pretty much like adware that doesn't need to be installed...
where did you see http://thinkminimo.com?