Fork me on GitHub
#boot
<
2017-10-02
>
seancorfield05:10:59

@andrew.sharp57 I'm very confused about what you're asking here -- the way publish-local invokes uberjar, there is no project parameter involved.

seancorfield05:10:15

It seems like you would need publish-local to take version and namespaces args, and then pass those and project to the uberjar call...

andrew.sharp5705:10:49

@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})

andrew.sharp5705:10:38

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})

seancorfield06:10:35

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?).

avabinary06:10:39

what's the recommended practices when trying to build a jar ?

avabinary09:10:09

i want to compile cljs

avabinary09:10:22

(cljs :optimizations :advanced)

avabinary09:10:36

to my build task

avabinary09:10:15

and the output says compiling cljs, some Duplicate external input: ... and when I launch, i get 404 on html pages requiring .jss

avabinary10:10:43

ah nevermind, my (cljs..) was after (uber)(jar) in my build task

avabinary11:10:30

i ran into another issue now

avabinary11:10:50

I want to pack some namespaces depending on user choices (sort of like addons)

avabinary11:10:12

and I can't seem to be able to compile them using the target dirs

avabinary11:10:17

can anyone help me ?

alandipert14:10:53

avabinary you could write a task that conditionally adds a directory to the fileset perhaps

kommen14:10:20

how can I stop a task when I start it from the boot repl, with something like (def dev (future (boot (watch) (cljs))))?

alandipert15:10:33

(future-cancel dev) would do it

kommen15:10:40

@alandipert thx!

fiddlerwoaroof18:10:34

Is there a way to invoke a boot task from maven?

richiardiandrea21:10:11

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 boot-clj 😄

phreed22:10:01

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.

ag23:10:11

why does adzerk-oss/boot-cljs-repl rebuilds stuff when run (start-repl)? does it have to recompile?

danielcompton23:10:07

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?

martinklepsch07:10:15

Is test the plain task from boot-test or something else you defined yourself?

danielcompton18:10:54

Plain task from boot-test

richiardiandrea19:10:00

I have never noticed that, by compile you mean aot compile or cljs compile?

danielcompton19:10:22

By compile I just mean load all the files

richiardiandrea19:10:47

Ok I will try that and get back to you