Do I have to specify a version for every dependencies? Is it possible to express certain version and up?

@leira https://dev.to/ebud7/maven-version-ranges

Using them makes dep resolution non-deterministic which is why people tend to avoid

Thanks No Java background here... so the version format is from Maven, that's the reason I didn't find any boot doc talking about this

I agree, it's not a good idea to have version range in projects I'm adding some tool task into profile.boot, like boot-new

No problem. Feel free to add to wiki in the place you expected to find 😀

And yeah, that makes sense

so the refresh task seems to be randomly failing. Certain namespaces simply stop updating, even if I add a whole new symbol. Running (boot (refresh)) shows that the namespaces are being updated, but the boot repl still has the old values. Is this a known issue?

Is there anyway to run a watch task "in the background" from a boot repl? I've started a repl and I wanted to start a file watcher but in the same jvm as the repl

@donyorm I assume you don't want to use watch, so what you can do is to run whatever task (even the repl) in a future so that you "free up" the main thread and can launch a second pipeline. Alternatively boot.parallel provides a way to launch tasks in parallel

right, that works well. I wasn't think of using boot tasks as code. I did want to use watch, I just needed to stick it in a future. Thanks!

Is there anyway to make the watch task run arbitrary code as opposed to another task?

@donyorm wrap it in a task

(with-pass-thru _
  (run-things))

for this task https://github.com/boot-clj/boot/wiki/Using-Boot-in-a-Leiningen-Project would it be the same if you wrapped the body in the with-pass-thru instead of returning the identity fn?

now that we have https://github.com/clojure/tools.deps.alpha we should port boot's better reporting I guess 😉

@richiardiandrea what are you referring to with boot’s better reporting?

I mean that boot has a very nice way of reporting dep download (on -v or -vv)...

ah! 🙂