When in a JVM project, what makes gradle/maven pul...

# kotest

[Emil Kantis]

When in a JVM project, what makes gradle/maven pull in kotest-*-jvm rather than just kotest-*? I have noticed I have an issue where kotest-runner-junit5 is pulled in as kotest-runner-junit5-jvm but kotest-assertions-json is just added as-is and I can't use it as a result.. 😕

[sam]

Gradle knows because of this "attribute" thing it supports

[sam]

the kotlin gradle plugin is configuring it behind the scenes

[Emil Kantis]

hmm, okay

[sam]

You can always force it by adding -jvm to the dependency

[Emil Kantis]

yeah, I did that for now.. just confused why:
• it's working in 1 project but not another 1
• why all other kotest dependencies are added correctly, but not this one

[Emil Kantis]

some gradle cache issue perhaps..

[sam]

perhaps, I think its all a bit black magic

[sam]

and in general I think gradle is the worst designed API/DSL on the planet

[sam]

worse even than sbt

[Emil Kantis]

but you still use it for kotest iirc? 🙂 personally I like it, I can't stand the verbosity of maven..

[Emil Kantis]

But I've seen how some abuse the extensibility of gradle to make it a nightmare..

[sam]

I use it because you need to if you want a multi platform project

[sam]

and it's not even the extensibility for me. It's the fact the DSL is so badly designed with confusing nomenclature, then combined with the disaster that is groovy

[Sourabh Rawat]

@sam do we(generally speaking) have a better build system than gradle? I am not very experienced other build systems. I tried maven in some projects. Immediately, wrote a migration to gradle.
But yes, groovy was a bad bad choice.

[sam]

I prefer maven because it's declarative so you don't have the power of a full language, but that's an unpopular opinion because... Xml I guess?

[Sourabh Rawat]

XML yeah. A pom.xml just feel bloated with tags to me.

[sam]

they could support yml