This message was deleted.

Yes, you can do that in a settings script. Or you just use the conventional default path for the version catalog which is

gradle/libs.versions.toml

, then you don't need the snippet at all. 🙂

thanks for the quick response, i don’t think i provided enough information. We operate with a monorepo and have various separate projects and try to isolate shared logic into plugins (and sometimes init scripts). We want to share version of common libraries between all of the projects. What we do today is copy and paste that block which refers to a common location in the mono repo. However, i need to add that block to each project. I’m asking how to reduce that duplication

Yeah, you can use a settings plugin for that.

i have heard reference to that in various stack over flow. is there a specific gradle doc on that? i haven’t been able to find one with google

What is "that"?

a “settings plugin” how is that different from a non-settings plugin which i have created

If we are talking about a "normal" plugin, it is

Plugin<Settings>

instead of

Plugin<Project>

. If we are talking about a precompiled script plugin, it is

foo.settings.gradle.kts

or

foo.settings.gradle

instead of

foo.gradle.kts

or

foo.gradle

.

excellent. we typically do precompiled scripts, so i’ll dig into that. thanks you

Example where this is done in a settings plugin: https://github.com/jjohannes/idiomatic-gradle/blob/main/gradle/settings/src/main/kotlin/com.example.repositories.settings.gradle.kts#L13-L16 And here we were just discussing even more options on how to structure such things: https://github.com/jjohannes/idiomatic-gradle/issues/4#issuecomment-1424765246