hello! can someone point me to a quick example of how to execute clojure code via boot (in the context of the project, ie with its dependencies)?

similar to lein run -m my.ns/fn with some args and from within a boot task if possible

don't know where to look

(require 'my.namespace)
(deftask run []
  (with-pass-thru _
    (my.namespace/-main)))

is all I found, don't understand why the require is in the boot file though?

how would I pass the CLI args to -main? boot seems to want me to specify them for the task

@thheller would you pass CLI args as a single string?

the issue here is probably that the boot invocation syntax is boot task1 —option value task2, i.e. if a “word” of the arg-string isn’t following an option it’s interpreted as a task

at the moment its just one string yes, not too sure about CLI opts yet

so there is no direct equivalent to lein run? I have to deftask it?

(deftask run 
  [o opts OPTIONS str “Your options]
  (with-pass-thru _
    (my.namespace/-main opts)))

boot run -o “--option value” 

@thheller ^ does this help?

@martinklepsch it'll do, not really using boot ... just comparing to lein and checking that things are possible in boot as well without too much work

@thheller cool, looking forward to see what you’re cooking up 🙂 feel free to ping me here if you have any questions

How do we know what the boot scopes are? So I can have [spyscope “0.1.5” :scope “dev”]?

And how do I know that there’s a dev (or any other) scope?

@twashing that's a general Maven concept, not specific to boot

Ah ok.

https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

however, most of it isn't relevant to boot

everyone uses maven repositories to distribute artifacts now, even if you don't use maven the build tool

but maven repos were originally created to work with maven the build tool

I just want to include spyscope for development, but not production.

that's not what scopes are for

Right. That makes sense.

Hmm ok.

so what you'd do is just conditionally include them in your dependencies

since you're programming in clojure in your build.boot

you can do anything

here is a sample, one sec

@twashing ^^

@micha Whoa! Sweet :)

I see where you’re going with this. Thanks!

barp $ is my shell prompt

I thought it was an arp command that shifted $1 of every transaction to …

Meh. Bad joke. Never mind :)

hahah

lol barp

has anyone seen this? for whatever reason adzerk/boot-cljs throwing exception java.lang.ClassCastException: clojure.lang.PersistentVector cannot be cast to clojure.lang.Symbol. I can’t figure out what change that causing this

are you doing (defn [x] ... somewhere?

definitely seems like a macro issue anyway

agree, vector and symbols, been there many times 😄

oh, right… it does look like that thing, let me see who’s that sucker intelligent person who broke it

boot-cljs is throwing this? not your source?

check your .cljs.edn files for a sym where you should have a vector?

@ag Does the exception have any file/line info and stacktrace?

@ag environ.boot/eval2342/fn/environ-middleware/environ-handler/fn boot.clj: 39

It is suspicious

that's probably just because of task middleware stack

But might be totally off actually

Yeah

@ag What value does your .cljs.edn have for :require property?

ah yeah i bet it's like :require [[foo.bar :as bar]] maybe

oh, ok… i found the issue… someone trying to add migrations with flyway, changed resources path

prob. boot needs better error message when can’t find .edn file

Hmm, boot-cljs should work fine without cljs.edn file

Shouldn't at least cause this problem

yah. for whatever reason things broke when :resource-paths #{”resources/public”} changed to #{”resources”}

¯\(ツ)/¯

for posterity and those of us committed to making all possible mistakes, can you tell us exactly what caused the problem? the masses yearn.

i would not expect a mere change in paths to produce that error.

we can put it on the wiki under troubleshooting.

q for the room: I've just implemented my first boot task, which examines my source files and does some special checks on the data within, and i want this task to either 'pass' and or 'fail' much like running a unit test suite. At the moment it just prints out pass/fail, but can you recommend a way to make it truly 'fail' and abort the rest of the pipeline?

you can always throw an exception

that will terminate the pipeline unless some other task upstream catches it

the watch task, for example, will catch exceptions

and print the stack etc

yea, i can work w/ that, though i'm still wondering if there's a more canonical way to fail a task

exceptions are a good way to do nonlocal return

like to abort something with prejudice

imho 🙂

most of the built in tasks have assertions in them

okay cool, well thanks for yho