Allow injection of dependency versions from command line for central declaration of dependencies

[ZakTaccardi]

Central declaration of dependencies is an awesome feature! However, we have the need to inject different values via local.properties/gradle.properties/command line

Will custom dependency versions be injectable via gradle properties/local.properties?

No, this is out of scope of this version. We are thinking about standard ways to do it, to address the use case of testing a new version of a library.

#15352 (comment)

We currently have something like:

// gradle.properties
ANDROID_GRADLE_PLUGIN=4.1.2

But AGP released a new version! So I would like to test it via

// local.properties
ANDROID_GRADLE_PLUGIN=4.1.2

or command line (more useful for CI):

./gradlew app:assemble -PANDROID_GRADLE_PLUGIN=4.2.1

We would like to see both these use cases supported officially with the Central Declaration of Dependencies.

[ZakTaccardi]

I think because .toml values can be overridden (let me know if I'm incorrect here), we could do something like the following:

from(files("../gradle/libs.versions.toml"))
from(files("../gradle/libs.local-versions.toml"))

And the libs.local-versions.toml would override the duplicate values from libs.versions.toml.

So the local.properties concept is already supported, if I understand correctly. However, it would be great to support from the command line too

[JavierSegoviaCordoba]

I am currently doing this:

// gradle.properties

javierscGradlePlugins=0.1.0-alpha.30

// buildSrc/settings.gradle.kts

val input = FileInputStream(file("../gradle.properties"))
val properties = Properties().apply { load(input) }
input.close()

val javierscGradlePlugins: String = properties.getProperty("javierscGradlePlugins")

dependencyResolutionManagement {
    repositories {
        mavenCentral()
    }

    versionCatalogs {
        create("pluginLibs") {
            from(files("../plugins-catalog/build/catalogs/libs.versions.toml"))
            version("javierscGradlePlugins", javierscGradlePlugins)
        }
    }
}

In my case I am not overriding it via CLI, but `./gradlew build -P"javierscGradlePlugins"="0.1.0-alpha.29" should work.

In the root settings.gradle.kts file in another project, I am using it without problems too, but the setup is simpler using by settings

// gradle.properties

massiveCatalogs=0.1.0-alpha.29

// settings.gradle.kts

dependencyResolutionManagement {
    repositories {
        mavenCentral()
        google()
        gradlePluginPortal()
    }

    versionCatalogs {
        val massiveCatalogs: String by settings

        create("libs") { from("com.javiersc.massive-catalogs:libs-catalog:$massiveCatalogs") }

        create("pluginLibs") {
            from("com.javiersc.massive-catalogs:plugins-catalog:$massiveCatalogs")
        }
    }
}

EDIT: well I am using it for settings the version of the catalog itself, not a version inside it, but I could use the version function to override a version as I used in buildSrc/settings.gradle.kts but just with by settings.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[gildor]

How can we prevent this feature from being closed?

I think the easiest solution is to have some convention for this, like for gradle properties, something like GRADLE_VERSION_CATALOG_$catalogName_$versionName

It's pretty common requirement, when we want to run tests on CI with updated version of some library