HOWTO: support gradle.properties for dependency version variables? #33957
Replies: 3 comments
-
Needs a reproduction repo -> https://github.com/renovatebot/renovate/blob/main/docs/development/minimal-reproductions.md |
Beta Was this translation helpful? Give feedback.
-
Here are some practical references:
|
Beta Was this translation helpful? Give feedback.
-
Hi there, Get your discussion 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. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
A Mend.io-hosted app
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitHub
Please tell us more about your question or problem
I have a Gradle project that contains a
deps.gradle
file. This file has the following definition:Various sub projects reference this as:
implementation libraries.example
. Then, there is a gradle.properties file that hasexampleVersion=1.2.3
.I have tried various forms of regex matchers to capture the dependency and link it to the right version variable, but from what I can gather, this scenario is not supported by renovate. Is that correct? Do you see a way I could support this form of configuration?
PS Switching to Gradle's version catalog at the moment is not possible, since the catalog does not centrally support exclusions.
Logs (if relevant)
No response
Beta Was this translation helpful? Give feedback.
All reactions