Splitties / refreshVersions

Life is too short to google for dependencies and versions
https://splitties.github.io/refreshVersions/
MIT License
1.63k stars 107 forks source link

Support - Declaring a version catalog #684

Open hanrw opened 1 year ago

hanrw commented 1 year ago

I have a Declaring a version catalog below

dependencyResolutionManagement {
    versionCatalogs {
        create("extraLibs") {
            from(files("gradle/extra.libs.versions.toml"))
        }
    }
}

gradle refreshVersions may update the version under gradle/extra.libs.versions.toml as well.

LouisCAD commented 10 months ago

Hello, sorry for the silence all the time. Do you still need the feature? If so, please let me know, I have several API design questions as Gradle APIs don't allow us to recover the file from version catalogs, which mean we would need to add a middleman.

hanrw commented 10 months ago

Thanks for checking this issue. I would say it's nice to have. I had rollbacked from using different versions.toml files.

vnickolov commented 4 weeks ago

Hello, I came across this issue and it is exactly what we need, we cannot use a single default libs.versions.toml because of some internal reasons and we have separate versions catalogs. It would be really great if we can specify additional catalogs to the refreshVersions configuration.

hanrw commented 2 weeks ago

i have a catalog project structure looks like below, would like to if can apply refreshVersions for each sub projects refreshVersions should able to update common and testing modules lib versions

catalog
 - settings.gradle.kts
  - include(":common")
  - include(":testing")
 - common
   - gradle/libs.versions.toml
 - testing
   - gradle/libs.versions.toml