A modern programming language that makes developers happier.

kotlinlang

Hello good people. Is it possible to have 2 _versions catalog_ ( or some trick to merge two of them )?

The scenario is:
We have the `main` project and a `sub` project as a submodule.
Having different dependency versions caused some troubles, so we wanna align them.
`sub` will have some dependencies in its _toml_ file, but `main` would need some dependencies that are not available in `sub`

That was possible before but it was removed, not sure why cc  <@U19Q5CC4S> 

Yes, you can have any amount of version catalogs without problem

What <@UE206C71V> is referring to is, that you cannot combine / merge multiple toml files into one version catalog easily. But having multiple version catalogs coming from multiple toml files is no problem at all.

How to do that? I tried adding 2 `create` but gave me an error

&gt; Invalid catalog definition:
&gt;   - Problem: In version catalog libs, you can only call the ‘from’ method a single time.

But actually I just noticed that changing name to `libs` it works :confused:

like
```dependencyResolutionManagement {
  versionCatalogs {
    create("someLibs") { // before libs
      from(files("gradle/libs.versions.toml"))
    }
    create("coreLibs") {
      from(files("sub/gradle/libs.versions.toml"))
    }
  }
}```

`libs` implicitly imports `gradle/libs.versions.toml` if it exists, so you cannot import another and thus second file into that catalog. The error is a bit misleading and will hopefully be changed.

So basically `libs` is always created by defo?

So if you want that `libs`, just remove it from your code as it is created automatically

Convention over configuration like everywhere in Gradle

Ok, I see! If the file exists then it’s different! Because I got this in pet-project
```dependencyResolutionManagement {
  versionCatalogs {
    create("libs") {
      from(files("../gradle/libs.versions.toml"))
    }
  }
}```
That’s why I got confused