Fork me on GitHub
#babashka
<
2021-04-16
>
borkdude10:04:14

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

borkdude10:04:54

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

borkdude10:04:54

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

grazfather14:04:44

told you so 😉

grazfather14:04:12

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

borkdude14:04:23

I also educated one of my colleagues to not use

release: clean test
    dothejob

borkdude14:04:28

to not depend on clean this way

grazfather14:04:48

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

grazfather14:04:15

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

Teemu Kaukoranta12:04:02

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

littleli12:04:24

it's newly available in the latest release