This message was deleted Gradle Community #general

Join Slack

This message was deleted.

# general

Slackbot

04/27/2022, 1:15 AM

This message was deleted.

grossws

04/27/2022, 2:38 AM

Why do you use programmatic way to build a version catalog? Usually you can just create

toml

file (

gradle/libs.versions.toml

would be automagically imported as

libs

catalog) and define it there like this:

Copy code

[versions]
assert4j = "3.22.0"
[libraries]
assertj-core = { module = "org.assertj:assertj-core", version.ref = "assert4j" }

API is useful if you want to build catalog from other meta sources, using loops etc. And please don't split messages, either edit original or add info in the 🧵. Else it make harder to follow the context and can split discussion.

grossws

04/27/2022, 2:41 AM

As for junit5 you don't really need in in the catalog anymore. You could just use:

Copy code

testing.suites {
  val test by existing(JvmTestSuite::class) {
    useJUnitJupiter(libs.versions.junit5.get()) // or just useJUnitJupiter("5.8.2")
  }
}

grossws

04/27/2022, 2:42 AM

And you are correct about bundles. They are effectively list of dependencies and you only can add all list to some configuration but not split it into several ones.

Norbert Kiesel

04/27/2022, 4:49 AM

I used the programmatic way because I like the auto-completion (and detection/avoidance of typos) of "real" variables. But yes, I ultimately have to extend this to 15+ repos with 250+ dependencies, so a shared

toml

file seems the right approach. Split messages: I thought of this as 2 separate questions, not a follow-up. But I for sure will follow your advice.

Open in Slack

Previous Next