A modern programming language that makes developers happier.

kotlinlang

I think this <https://github.com/kotest/kotest/issues/4596|issue> was caused by changing the BOM <https://github.com/kotest/kotest/commit/5206d449ee5652e4716b1e654a5a5329484cec5b|here>. Anyone got pointers on how I can start to fix it? And as the original thread author mentions, should we just replace the BOM with a gradle version catalog?

I really like gradle versions catalogue.

Kotest is very gradle-oriented, Kotlin in general is gradle-oriented.

Version Catalogs are a new feature, it's unlikely that it will be abandoned soon

I've never used a published version catalog, but I did want to publish a kotest catalog a while back.. never got it to fully work though :confused:

I still think providing a BOM is nice for users who prefer that. It's not mutually exclusive with providing a catalog. And the BOM works with both Gradle + Maven..

Just don't know why its broken, and I don't know anything about BOMs

Looks like some advanced gradle shizzle .. I'll see if I can figure it out, but I think Adam would be able to solve it with ease

<https://github.com/kotest/kotest/pull/4751>

well it was quite a hacky fix.. :see_no_evil:

The reason it works is cause we do the publish -jvm-variants in root jars thing.. so we just need to refer to the root jars instead of the -jvm ones