@onetom the boot cat is not named afaik

Is there a way to exit a boot process with an error but without printing a stack trace?

Nope; https://github.com/boot-clj/boot/issues/486

I did implement implement the stack trace part of the issue here: https://github.com/boot-clj/boot/compare/feature/exception-handling

hey guys, anyone knows whether getting cloverage running in combination with boot is possible ? it seems to only have a lein plugin

@lmergen There is a PR at Cloverage repo: https://github.com/cloverage/cloverage/pull/115/files

ah, that looks like what i want

looks like the original committer of that PR is busy with other things, guess i should ping him

Is there a doc about scopes somewhere?

I’m not sure when to use :scope “test" and which other options are available

I'd guess provided, runtime, etc, but how does it works with boot?

@lsenta here are the official docs: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

the most significant thing to note is probably that dependencies with :scope "test" are not registered as transitive deps. E.g. A depends on B with scope test. C depends on A. When C downloads all of A dependencies B is not regarded as necessary dependency

@martinklepsch How do you check / change which scope you’re in?

Say I have a (deftask dev [] (comp live cljs server)), can I make sure it loads the devtools deps or any other :scope “test” resources?

when you load them yourself using set-env! they're loaded no matter which scope they have

Got it, that’s something you care about when you have to finetune jars / class files / dependencies

Thanks a lot for making this clear @martinklepsch 🙂

scopes are mostly related to how dependencies are treated when they show up during dependency resoution

you're welcome @lsenta