This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-19
Channels
- # aws (4)
- # aws-lambda (2)
- # beginners (67)
- # boot (38)
- # cider (32)
- # cljs-dev (12)
- # cljsrn (2)
- # clojars (2)
- # clojure (190)
- # clojure-chicago (1)
- # clojure-dusseldorf (2)
- # clojure-germany (1)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-russia (6)
- # clojure-spec (47)
- # clojure-uk (10)
- # clojurescript (59)
- # cursive (9)
- # data-science (14)
- # datomic (24)
- # devops (16)
- # emacs (8)
- # fulcro (25)
- # graphql (30)
- # hoplon (123)
- # juxt (15)
- # lambdaisland (2)
- # leiningen (4)
- # luminus (6)
- # lumo (9)
- # off-topic (11)
- # om (7)
- # onyx (8)
- # re-frame (14)
- # reagent (5)
- # ring-swagger (5)
- # shadow-cljs (46)
- # spacemacs (41)
- # specter (8)
- # testing (8)
- # unrepl (31)
- # yada (18)
if I have something like (def p (future (boot (watch ,,, etc
how can I "unbind" it, so it kills the watch?
Anybody know of a good clojure library for manipulating jar files, making custom jar files etc?
when I execute jar with boot the jar file does not include the source code of my project
@nick319 the source code usually does not get included because of its role in boot
. https://github.com/boot-clj/boot/wiki/Filesets#roles-of-files
so for the to be included, you need to add them to :resource-paths
@richiardiandrea I see, so that is why people use the aot task when using jar usually?
uhm...no well that's a separate requirement I guess, aot
should just compile to Java
I personally rarely use aot
yep if the code is reshared in a lib
@nick319 the wiki is good enough I'd say
@richiardiandrea do you know?
@nick319 the default namespace is boot.user
so every def in build.boot
should go there
is it a question? 😄
I asked a question yesterday that did not get a response. Let me try to ask more carefully.
There are pre-tasks
, post-tasks
, pre-post-tasks
and control-tasks
. https://github.com/boot-clj/boot/wiki/Tasks
Do these designations cover all cases?
In particular, are there tasks that continue running after they have finished their post
phase?
do you need such a task @phreed?
there's nothing stopping you making such a task if you need to, except perhaps the termination of the vm
I am interested in producing an intermediate watcher. `(deftask foo [] (comp (wait) (watch :source #{"build.boot"}) (reload-boot) (watch :source #{"src/antlr-lexer/"}) (antlr4 :lexer ["Lexer.g4"]) (watch :source #{"src/antlr-parserer/"}) (antlr4 :parser ["Parser.g4"]) (watch :source #{"src/java/"}) (javac) (test-rig :parser "org.aql.AqlParser") (target :dir #{"target"}))) ` For this example it is not that important but in some cases the tasks can be expensive.
@mccraigmccraig Does't repl
do something like that? (leave something running past the post
phase, namely the server) Does it matter where in the pipeline the repl
task is placed? I am trying to get some insight into how the repl
interacts with other tasks, realizing it has a server mode that gets activated on the pre
pass and a client mode that gets activated on the post
pass.
i don't think i understand @phreed - gtg too, so maybe someone else can help