-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve dynamic deps versions in gradle #15359
Comments
I think you should prefer gadle versions catalog, which is already supported by renovate https://docs.gradle.org/current/userguide/platforms.html#sub::toml-dependencies-format |
Is there a long term reason to use gradle this way instead of v7's central dependencies file? |
I'll certainly try to use https://docs.gradle.org/current/userguide/platforms.html#sub::toml-dependencies-format |
@viceice Does it have to be in toml? I have implemented it in groovy and Renovate onboarding says:
for dependencyResolutionManagement {
repositories {
mavenCentral()
}
versionCatalogs {
libs {
def log4j = '2.17.+'
library('log4j-core', 'org.apache.logging.log4j', 'log4j-core').version(log4j)
}
}
} |
i think we only support the toml file. |
Are there any plans to support Groovy or Kotlin since they're the main languages people use for Gradle definitions? |
In short: maybe not. We certainly don't want to have to execute kotlin or groovy code just to work out what dependencies you're using when there's a simpler alternative having toml |
Understand, will try to move to toml then. Having Renovate working is more worth than using common language/format. |
What would you like Renovate to be able to do?
In build.gradle I do this:
gradle/dependencies.gradle:
I'd like Renovate bot to be able to pick log4j version and update it automatically.
Or is there another way to declare deps version in similar manner that Renovate supports?
Is this a feature you are interested in implementing yourself?
No
The text was updated successfully, but these errors were encountered: