This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-02
Channels
- # beginners (98)
- # bigdata (1)
- # bitcoin (1)
- # boot (32)
- # cider (20)
- # cljs-dev (57)
- # cljsrn (130)
- # clojure (93)
- # clojure-dusseldorf (1)
- # clojure-germany (1)
- # clojure-greece (3)
- # clojure-italy (2)
- # clojure-russia (203)
- # clojure-spec (14)
- # clojure-uk (50)
- # clojurescript (127)
- # css (7)
- # cursive (6)
- # data-science (1)
- # datomic (4)
- # emacs (1)
- # events (1)
- # fulcro (8)
- # funcool (12)
- # graphql (7)
- # jobs (1)
- # lein-figwheel (2)
- # luminus (2)
- # off-topic (7)
- # om (16)
- # onyx (4)
- # parinfer (17)
- # pedestal (6)
- # portkey (36)
- # proton (3)
- # re-frame (10)
- # shadow-cljs (140)
- # spacemacs (12)
- # specter (1)
- # sql (1)
- # vim (10)
- # yada (10)
@andrew.sharp57 I'm very confused about what you're asking here -- the way publish-local
invokes uberjar
, there is no project
parameter involved.
It seems like you would need publish-local
to take version
and namespaces
args, and then pass those and project
to the uberjar
call...
@seancorfield that’s about right, except that i expect another task, publish-remote
, which would be like (comp (uberjar) (push))
. this is why i have the parameters on uberjar
instead of publish-local
. if i put them on publish-local
, i’d have to duplicate them for publish-remote
.
ideally, uberjar
would take these parameters, and both publish-local
and publish-remote
would obtain them by running uber jar, like
(task-options! uberjar {:project 'group.artifact})
then when we (comp (uberjar) (install))
or (comp (uberjar) (push))
we can get the project
parameter out of uberjar
, somehow. at least, that’s how i’d like it. otherwise users have to do something like
(task-options!
uberjar {:project 'group.artifact}
publish-local {:project 'group.artifact}
publish-remote {:project 'group.artifact})
Take a look at the source of task-options!
-- maybe you can figure out how to get the default options for uberjar
within another task (since it seems you're only relying on the default?).
and the output says compiling cljs, some Duplicate external input: ...
and when I launch, i get 404 on html pages requiring .jss
avabinary you could write a task that conditionally adds a directory to the fileset perhaps
how can I stop a task when I start it from the boot repl, with something like (def dev (future (boot (watch) (cljs))))
?
(future-cancel dev) would do it
Is there a way to invoke a boot task from maven?
I have released boot-figreload
0.5.13
and pushed a 0.5.14-SNAPSHOT
for folks to try out https://clojars.org/powerlaces/boot-figreload 😄
I am writing some tasks for working with Antlr4. There is something wrong with the produced fileset (it does not contain my generated java). I have been using util/info, boot/user-files, boot/output-files, boot/input-files, etc. Specifically, I would like to preserve the tmp-dir beyond the task lifespan. I would appreciate any other advice on task debugging as well.
why does adzerk-oss/boot-cljs-repl rebuilds stuff when run (start-repl)
? does it have to recompile?
I'm finding that if my Clojure project can't compile when running $ boot test
then boot just hangs instead of exiting. Is this expected behaviour, or am I doing something wrong?
Is test
the plain task from boot-test or something else you defined yourself?
Plain task from boot-test
I have never noticed that, by compile you mean aot
compile or cljs compile?
By compile I just mean load all the files
Ok I will try that and get back to you