multimodule gradle (kotlin) with versions defined as constants in buildSrc

[toelen]

When using gradle multimodule in kotlin, it is common practice to define dependency versions as constants in the buildSrc.

buildSrc/src/main/kotlin/Dependencies.kt:

object Libraries {
        object Versions {
            const val jackson = "2.9.10"
        }

    const val jacksonAnnotations = "com.fasterxml.jackson.core:jackson-annotations:${Versions.jackson}"
    const val jCache = "javax.cache:cache-api:1.1.0"
}

this constant can be used like this

build.gradle.kts:

implementation(Libraries.jacksonAnnotations)

Right now this is not picked up by renovatebot. gradle useLatestVersions does pick it up however, so I assume renovatebot does not look at the buildSrc directory

[ikesyo]

Yes this is not supported yet. See the discussion in #4086 (comment) for the details.

[toelen]

Does this mean the following syntax is supported const val jCache = "javax.cache:cache-api:1.1.0" (without the separate constant with only the version) but we need to add buildSrc to the fileMatch ourselves?

[ikesyo]

@toelen Exactly.

const val jCacheVersion = "1.1.0"
const val jCache = "javax.cache:cache-api:$jCacheVersion"

is also supported (without property access).

[rarkins]

As a workaround it should be possible to add a custom rule using our new regex-based manager: https://docs.renovatebot.com/modules/manager/regex/

[rarkins]

FYI we have migrated to a JS-based parser for Gradle now, and would implement it there instead of the previous approach

[vaclavbenes]

Hi, Does it work with the latest version or its still unresolved? I have similar setup with dependencies store in buildSrc and latest 32.82.0 cant find them.

DEBUG: Applying enabledManagers filtering (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: \.gradle(\.kts)?$ for manager gradle (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: (^|\/)gradle\.properties$ for manager gradle (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: (^|\/)gradle\/.+\.toml$ for manager gradle (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: \.versions\.toml$ for manager gradle (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: (^|/)buildSrc/.*.kt for manager gradle (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: (^|/)gradle/wrapper/gradle-wrapper.properties$ for manager gradle-wrapper (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: (^|/|\.)pom\.xml$ for manager maven (repository=benesv/avast-android-test-utils)
DEBUG: Using file match: ^(((\.mvn)|(\.m2))/)?settings\.xml$ for manager maven (repository=benesv/avast-android-test-utils)
DEBUG: Matched 8 file(s) for manager gradle: build.gradle.kts, buildSrc/build.gradle.kts, buildSrc/settings.gradle.kts, buildSrc/src/main/kotlin/Dependencies.kt, demoTest/build.gradle, gradle.properties, settings.gradle.kts, utils/build.gradle.kts (repository=benesv/avast-android-test-utils)
DEBUG: Matched 1 file(s) for manager gradle-wrapper: gradle/wrapper/gradle-wrapper.properties (repository=benesv/avast-android-test-utils)
DEBUG: Found gradle-wrapper package files (repository=benesv/avast-android-test-utils)
DEBUG: Found 1 package file(s) (repository=benesv/avast-android-test-utils)
DEBUG: Manager explicitly enabled in "enabledManagers" config, but found no results. Possible config error? (repository=benesv/avast-android-test-utils)
"manager": "gradle"
DEBUG: Manager explicitly enabled in "enabledManagers" config, but found no results. Possible config error? (repository=benesv/avast-android-test-utils)
"manager": "maven"
INFO: Dependency extraction complete (repository=benesv/avast-android-test-utils)
"baseBranch": "master",
"stats": {
"managers": {"gradle-wrapper": {"fileCount": 1, "depCount": 1}},
"total": {"fileCount": 1, "depCount": 1}
}

[github-actions]

Hi there,

Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team