This message was deleted.

I thought this might be better, but I think it may require first publishing the catalog, which would be less than ideal.

Docs on declaring dependencies between projects. Something like:

dependencies {
   implementation(project(":catalog"))
{

I don't think this creates a version catalog though, since the

version-catalog

plugin docs say you need to specify it like so:

catalog {
    versionCatalog {
        create("libs") {
            from(project(":catalog"))
        }
    }
}

which does not work.

The path I’d taken on that is publishing the version catalog to a maven repository (i.e., mavenLocal, a nexus repo, etc) and then you’d take it into projects you want to share it based on the group/artifact/version that is published.

Maybe using a composite build where

catalog

is included in

pluginManagement

so it can contribute to the

settings.gradle.kts

?

You could try to define catalog in settings (via toml or programmatically) then use it both in the platform project and use the VersionCatalogExtension to construct the same in your catalog. In some cases I just used programmatical access via the extension to configure platform too. Had to add some simple naming rules (BOM/plarform must have alias with -bom suffix) to construct platform correctly.