This message was deleted.

I suppose you could use a settings plugin to configure the version catalog (create another project with the plugin,

includeBuild

it in

pluginManagement

in your

settings.gradle.kts

and apply it; see https://github.com/gradle/gradle, and its build-logic-commons and build-logic-settings, used by the root project and build-logic) It's indeed much easier with a TOML file, and I'd say that unless you have specific needs you should probably use a TOML file.

I have seen that - I was wondering here if catalog defined in code can be somehow shared

dependencyResolutionManagement {
    versionCatalogs {
        create("libs") {
            version("kotlinVersion", "1.8.20")

            plugin("springframework-boot", "org.springframework.boot").version("3.0.5")

maybe as extension function in another included build which could be consumed in both settings files?

It depends on the situation. TOML is very simple, intentionally. For usual cases I'd also prefer it. API is there for more sophisticated needs like having an own format that needs to be parsed, or things that need to be calculated, ...