This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-11
Channels
- # aleph (7)
- # bangalore-clj (11)
- # boot (70)
- # cider (11)
- # cljsjs (3)
- # cljsrn (17)
- # clojure (88)
- # clojure-brasil (8)
- # clojure-dev (17)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-poland (8)
- # clojure-russia (2)
- # clojure-spec (44)
- # clojure-uk (32)
- # clojurescript (176)
- # cloverage (2)
- # component (5)
- # cursive (3)
- # datomic (23)
- # defnpodcast (6)
- # dirac (15)
- # emacs (6)
- # garden (19)
- # hoplon (126)
- # leiningen (1)
- # off-topic (3)
- # om (66)
- # onyx (56)
- # re-frame (8)
- # reagent (7)
- # ring-swagger (43)
- # specter (18)
- # untangled (110)
- # vim (3)
- # yada (39)
Hi all: I recently upgraded from using Boot 2.5.5 to 2.6.0, and saw that when running tests for one of my libraries, the :resource-paths
(as defined in the library's build.boot file) is no longer visible/defined, the process barfs with NPE when it's supposed to load files there. Reverting back to Boot 2.5.5 works ok. Any ideas? Checked https://github.com/boot-clj/boot/blob/master/CHANGES.md but didn't see anything pertinent to this problem...
@limist have you tried with creating a new dir, with a file in it and then doing
boot -B -r that-new-directory repl
;; then in the repl try
(slurp ( "that-file.txt"))
The -B
prevents your build.boot
from being evaluated, the -r
adds the directory to your resource paths
@martinklepsch Thanks, the code you suggested works fine, using Boot 2.6.0
can you provide your build.boot
(maybe in private if you prefer that)
@limist thanks!
@martinklepsch Thank you for the detailed help!
oh cool, if standalone might be worth maybe putting it in https://github.com/boot-clj/boot/wiki/Snippets
@richiardiandrea it has a home over here 🙂 http://github.com/degree9/boot-electron
ahahah
greeeeat
im working on a generic express server that can be auto included so you can build electron hoplon apps
way better...in this case maybe https://github.com/boot-clj/boot/wiki/Community-Tasks then
then I will tackle a nodejs port of castra 😛
I heard those are fun to work with, I guess you can confirm that
yeah i havnt played with nodejs too much other than cli apps, so this will be interesting
@flyboarder cool — so you could essentially build an electron app along with Hoplon?
right the idea is that hoplon does it’s thing as per usual, you just also get the option of launching it via electron just by adding the task
it works on my demo app, but nothing production yet
@flyboarder I’ve seen other electron-targetted cljs, but iirc not as simple as just adding a boot task, and it also has hoplon. Seems like a good idea
yeah I decided that the investment into running hoplon cross platform was well worth it
Hi boot friends. I’m using boot to build a couple of executable jars from a repo. Currently I have a build-client
and a build-server
task, which I combine into a build
task with comp
. Of course this doesn’t exactly do what I want because the second build winds up containing the first. Is there an idiomatic way to tell boot to run two independent tasks, either serially or, ideally, concurrently?
@donaldball you can run boot inside of boot to accomplish this
@donaldball here is a demo: https://github.com/micha/multi-module-build/blob/master/build.boot
the idea there is that you have one build.boot which is used in that example in 3 boot instances
there is the doit
task that is the one that starts nested boots to build alpha and bravo
also in that example there is a dependency relationship between alpha and bravo: bravo depends on alpha
cool, I get the gist
silly question, I would like to use two sounds for notify
and I put them in resources/boot/notify/
. Should it be enough then to use -T themename
?
I also tried boot watch test -f backend notify -a --soundfiles '{:failure "resources/boot/notify/music_failure.mp3" :success "resources/boot/notify/music_success.mp3"}'
without success
boot repl
isn’t giving me a repl with any of my project’s dependencies loaded…?
@donaldball how do you mean?
Just as I say. In my build.boot
I declare a normal dependencies vector via set-env!
which I would expect to be loaded when I run boot repl
, but I’m not seeing any of them, including the specified clojure version
I can replicate with just about the simplest possible build.boot
:
(set-env!
:dependencies '[[org.clojure/clojure "1.9.0-alpha12"]])
which suggests I’m misunderstanding something fundamental and simple 😛
@donaldball : clojure version depends on your boot.properties
file locally or on ~/.boot
Thanks, that was my error
@micha yes I can slurp it...weird, I'll dig
@donaldball you will want to have an explicit clojure dependency even though clojure is already loaded. this explicit dependency will control how transitive dependencies are resolved in the aether maven machinery
the dependency resolution machinery doesn't know that clojure is already on the classpath, so it will try to pull it in as a transitive dependency
got it, thanks
Speaking of aether, I just crashed on the shoals of jackson version conflicts away with the very latest s3-wagon-private
Has anyone run across a wagon impl that just shells out to the aws cli to do the work?
@donaldball have you tried the org.springframework.build/aws-maven
one?
doesn’t permit the use of sts credentials; hard requirement for us
I have forked it to work with a good combo of amazon+jackson, but that doesn’t work with the boot worker pod implicit dependencies
2.5.5
is what s3-wagon-private
now uses, or will when they release 1.3.0
it needs it; the amazon lib has a hard minimum requirement
I’m running boot repl
, and then from inside the nrepl, (boot (cljs))
. Everything works, except that CLJS compile warnings/errors go to the terminal, rather than my nrepl output. Is there a way to fix that?
FYI, I've deployed a snapshot of system
with a surprise feature. Lisp mode, recompile only (no usage of remove-ns
). Basically, this gives you a standard Lisp REPL experience where you recompile until it breaks. 😃
As usual, available from Clojars. Repo is here: https://github.com/danielsz/system