What I tend to do @qz is to have [a args ARG [str] "the arguments for the application."] as my run task argument specification and then (apply app/-main args) in the task.

Then you can do boot run -a foo -a bar -a quux etc

@seancorfield: i ended up making shebang script that loads build.boot and then runs app main. do you have to repeat “-a” for every param you want to pass to app?

@qz: Yes, because of the way task argument parsing works in Boot.

has anyone encountered this yet?

> boot show -d
             clojure.lang.ExceptionInfo: clojure.lang.ArityException: Wrong number of args (2) passed to: aether/dep-tree

Is it expected that boot repl takes 14 seconds to start on a reasonably fast computer?

@dottedmag: sounds ballpark, you can tinker with BOOT_JVM_OPTIONS to start faster - export BOOT_JVM_OPTIONS='-client -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -Xverify:none' https://github.com/boot-clj/boot/wiki/JVM-Options

but those options can introduce other problems

Have you guys ever had the following error (it appeared this morning here with 2.5.5):

Caused by: java.lang.ClassNotFoundException: mranderson046.toolsreader.v0v10v0-alpha3.clojure.tools.reader.impl.utils.TaggedLiteral
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at clojure.lang.DynamicClassLoader.findClass(DynamicClassLoader.java:61)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:348)
	at clojure.lang.RT.classForName(RT.java:2065)
	at clojure.lang.Compiler.resolveIn(Compiler.java:6921)
	at clojure.lang.Compiler.resolve(Compiler.java:6884)
	at clojure.lang.Compiler.analyzeSymbol(Compiler.java:6845)
	at clojure.lang.Compiler.analyze(Compiler.java:6427)

I heard they released tools.reader beta1 dunno if it can be related

it happens with boot -vvv cider repl wait

if I remove cider everything is fine, so ... sorry but this does not belong here I guess

I have been working on getting 'boot' to play nice with 'Atom:proto-repl'. https://github.com/jasongilman/proto-repl I am having some difficulty due to gaps in my understanding of how boot, leiningen and clojure set things up when they start. https://github.com/jasongilman/proto-repl-demo/issues/5 My immediate question is... What is this 'boot.user' namespace that boot starts with? What is wrong with the clojure 'user' namespace?

@jasongilman: hi, I am wondering if something like (comp (watch) (reload)) might be the way to go.

@phreed: the boot.user namespace is created by boot

the user namespace has historically been used for other things

so boot doesn't clobber that

@micha: what does boot put in the boot.user namespace?

type boot -vb foo bar

where foo and bar are whatever tasks you like

that will print the generated namespace

so you can see what it does

oh nice trick didn't know that!

@phreed: I think watch and reload could be one valid approach for use of boot and Proto REPL but I don't think that should be the default. What's the problem you're trying to solve?