Clojurians Log v2

I'm reconsidering the #{p1 p2} again. I wanted to also introduce (p1 p2) to force sequential execution (for things like clean), but I think this is getting too ambiguous when you have various nested dependencies. So I may drop #{p1 p2} altogether again. https://github.com/babashka/babashka/issues/792 cc @maxp @grazfather

Consider it deprecated today, I removed it from the docs.

So like @grazfather suggested: all tasks should be able to run in parallel and running in parallel is a top-level invocation option

so if you want explicit clean before anything else, use this: https://gist.github.com/borkdude/35bc0a20bd4c112dec2c5645f67250e3#file-bb-edn-L24

Added another example from work: https://gist.github.com/borkdude/35bc0a20bd4c112dec2c5645f67250e3

Hi! Any chance we could get java.security.SecureRandom added to babashka?

it's newly available in the latest release

https://clojurians.slack.com/archives/CLX41ASCS/p1618484480204200

haha

awesome

told you so 😉

:-D

naw, just kidding about gloating, but this is the way that makes more sense to me

I also educated one of my colleagues to not use

release: clean test
    dothejob

to not depend on clean this way

yep that’s a good way to slow your builds down 🙂

Make is very naive in that it only has phony targets and timestamps to use, that’s why I am excited about babashka