@borkdude I needed to do something that reminded me of what you were asking previously, ie. executing code in a library without requiring anything. In short, you can use resolve. You get hold of the Var, and then you can do what you want with it, function application (IFn), deref it if it's a reference value, etc. Of course, the definitions need to be present in the runtime when you do that.

@danielsz you still need to require the namespace the var is in

that's what compiles the clojure source

resolve lets you resolve the var by name at runtime

@micha you can provide a fully namespaced Var to resolve. No need to require the namespace as far as I can tell.

the var can't exist unless you compile the namespace

and add it to the namespace cache etc

something needs to eval the clojure source

@micha Ah, OK, but that can happen elsewhere, it doesn't need to be in the namespace where you resolve the Var.

that's true

tha's what require does though

it checks to see if the namespace was compiled already, if not it compiles it

@micha Yes, that's true.

@micha I actually am piggiebacking on a Var provided by boot.core, the warnings Var, but I don't want to require it, because it would break uberjars, so I use the resolve hack.

tricky 🙂

hehe, yeah 🙂 The beauty of a dynamic runtime.

you can still use require in a try/catch

for sanity

if the namespace isn't available on the classpath it will throw

@micha yeah, sure, that is possible too.

@micha When I run a deftask, I know that boot.core is available, so I opted for the resolve hack.

And it passes the uberjar creation process, because otherwise it throws a boot.core not found error.

Did anybody get anywhere with persistent boot caches & clojurescript? It would be nice to have a repeated cold-restart of boot skip rebuilding cljs from scratch.

Sometimes when I navigate to a definition (M-.) with CIDER I end up in the boot cache. What could be wrong here?

It may have something to do with hugsql

Heavyweight: boot dist --help 54.41s user 22.50s system 107% cpu 1:11.71 total

There must be some sort of caching we can do to make command --help take less than 70 seconds

Hey folks

How does one pass -D options too Boot? It doesn't seem to work through BOOT_JVM_OPTIONS

I'm trying to launch a Boot repl with JMX enabled, and the JMX socket doesn't get opened

BOOT_JVM_OPTIONS='-Xmx2g -client -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -XX:MaxPermSize=128m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xverify:none -XX:+PrintFlagsFinal -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=43210' boot repl

Sorry, my bad. Got confused with my own aliases

@alexyakushev your name always makes me think of "yak shave", which is pretty awesome

no offense intended ^^

Guilty as charged 😄

i met a dude once named "micha nikotin"

he won the name contest that day

we met while smoking

This is fate

what is the boot equivalent of lein check?

what is lein check? 😄

https://coderwall.com/p/04o8yq/lein-check

I used it to see if I had any bad typos in my code after refactoring something

like misspelled namespaces in require

interesting

don't know about an equivalent boot task

lein: check Check syntax and warn on reflection.

Sounds like kibit or eastwood?

https://github.com/tolitius/boot-check boot check

Hey, can anyone expand on the last section of this? https://github.com/boot-clj/boot/wiki/S3-Repositories

I'd like to try out the aws-maven thing, but it's not clear what I then need to put in my :repositories key to go with it

Aha, I got it, looks like I had the pathname slightly wrong, though I didn't get any feedback

hey guys… I can’t set task-options! for multiple tasks at once? gotta have separate call for each task?

@ag pretty sure you can: https://github.com/boot-clj/boot/blob/ac835cea8c18e926bb843e01579b86e3f30458d2/README.md#configure-task-options

also I can’t seem to be able to turn on verbose loggin for adzerk.boot-cljs from inside the .boot file

@ag What do you refer by boot-cljs verbose logging?

@ag you have to call your task before the tasks with options you are changing but you can do multiple ones with a single call

The instructions for running boot in circleci suggest using this stanza:

dependencies:
  pre:
    # Could use `latest` tag instead of version number
    - curl -L  -o ~/bin/boot
    - chmod +x ~/bin/boot
  override:
    # Run tests here so everything loaded by test task is cached
    - boot run-tests
  cache_directories:
    - "~/bin”

Why even bother caching ~/bin if we’re going to curl the shim each time?

Shouldn’t we be caching ~/.boot instead?

@flyboarder when I start repl and I have task-options! already in my build.boot. do I still have to call task-options! in the repl before starting a task?

@ag no your build.boot file is already processed by that point i believe

I am still struggling to set https://github.com/clojure/clojurescript/wiki/Compiler-Options#verbose for boot-cljs

in repl

(cljs :compiler-options {:verbose true})

yeah, I have that in both task-options! and in the task itself - still nothing 😞

oh I think it’s because I also have ../resources/js/dev.cljs.edn

compiler-options are merged, but currently options from .cljs.edn have priority

in next version task-options will have priority

So if you also define :compiler-options :verbose on .cljs.edn with current version, that will be used

so is there an easy way not to use cljs.edn at all? What would be correct way of putting this in build.boot:

{:require [sample-routing.core]
 :init-fns [sample-routing.core/init!]
 :compiler-options {:asset-path "js/dev.out" :verbose true}}

There is no support for require and init-fns without cljs.edn

oh.. alright

But to rephrase, if you don't define :verbose option on .cljs.edn you can set it on task options

that’s not working…

Can you paste your build.boot (at least cljs task call) and cljs.edn somewhere?

meh… it’s now working no matter where I put it… shows just this:

Compiling ClojureScript...
• js/dev.js
Sifting output files...
Writing target dir(s)...
Elapsed time: 37.131 sec

I am expecting to see verbose log

hold on… trying again…

nope… still nothing

this is what I have in .boot

…
(deftask dev []
  (comp
    (serve)
    (watch)
    (cljs-repl)
    (reload :on-jsload 'sample-routing.core/init!)
    (speak)
    (garden)
    (cljs :ids #{"js/dev"})
    (sift :move {#"dev.js" "main.js"})
    (target)))

{:require          [sample-routing.core]
 :init-fns         [sample-routing.core/init!]
 :compiler-options {:asset-path     "js/dev.out"
                    :parallel-build true
                    :verbose        true}}

(def p (future (boot (dev))))

Starting reload server on 
Writing adzerk/boot_reload/init27670.cljs to connect to ...

Starting file watcher (CTRL-C to quit)...

nREPL server started on port 51458 on host 127.0.0.1 - 
Adding :require adzerk.boot-cljs-repl to dev.cljs.edn...
Adding :require adzerk.boot-reload.init27670 to dev.cljs.edn...
Compiling styles.css...
Compiling ClojureScript...
• js/dev.js
Sifting output files...
Writing target dir(s)...
Elapsed time: 38.633 sec

This is working for me: https://github.com/Deraen/saapas/compare/cljs-verbose

nope… no matter where I put compiler-options - edn file, task, or task-options! the setting seems to be ignored.

Is this a reasonable change to have made?

https://github.com/boot-clj/boot/wiki/Running-Boot-on-CI-systems/2eacd003b889e0281ddb4fa53afdd05f485d974d

@donaldball caching ~/.boot/cache/tmp can potentially cache lots of unncessary files

ok.. I think it’s not showing verbose when boot connected via CIDER

is that possible?

Yeah, the travis one only caches /.boot/cache/bin and /.boot/cache/lib

Is there a reason not to cache ~/.boot/cache/cache ?

@donaldball boot/cache/cache contains all the temp dirs for each project, that is all the input files and all the temp dirs for all tasks etc.

lots of unncessary files

cool, thanks, I will correct circleci to simply match the travis recommendations then

@ag Hmm yes, cider-nrepl does some \out\ redirection

@ag are you using Cljs parallel build?

yup definitely when in cider… at least some cljs-build options getting ignored ;(

I doubt options are ignored, but it is possible that output is not correctly redirected if written in another thread

Boot-cljs in fact runs the Cljs compiler inside future so there is a good chance that that will break output redirection with Cider

Even if you don't use parallel build

oh shit… so I finally managed to see output when no parallel build and no future… but in the other buffer. in nrepl-server buffer

but… for whatever reason same thing in lein project works as expected

is that a bug in CIDER or boot-cljs?

@ag boot-cljs future use is my first guess. Not sure if this change makes any sense, but you could try it: https://github.com/adzerk-oss/boot-cljs/compare/future-out-binding

Clone, checkout branch, boot build and update your project to use -2-SNAPSHOT

@juhoteperi even when I start the task like (boot (dev)) it still outputs into wrong buffer

@ag How would you run lein-cljsbuild from cider-repl? doesn't it need its own lein process?

I'm off to bed, please comment on the issue if you find something.