Renovate fails to update maven property version in multi-module maven project #22171
Replies: 5 comments
-
Any public example or reproduction available? |
Beta Was this translation helpful? Give feedback.
-
@zharinov I thought we handled this case already? |
Beta Was this translation helpful? Give feedback.
-
Yes, it should handle it, so most probably there is a bug |
Beta Was this translation helpful? Give feedback.
-
In that case let’s wait for a reproduction or more details, if we already have known working cases too |
Beta Was this translation helpful? Give feedback.
-
@jamesmmchugh can you provide any more details? |
Beta Was this translation helpful? Give feedback.
-
What Renovate type are you using?
N/A
Describe the bug
GIVEN: If you have a multi-module maven project, where the parent (or any module that is higher in the dependency tree) module defines the artefact version as a property but doesn't use the property itself, and the downstream module inherits the property and uses it.
THEN: Renovate doesn't update the dependencies in the downstream module.
Did you see anything helpful in debug logs?
N/A
Expected behavior
Renovate should update the property in the parent/upstream module.
Screenshots
N/A
Additional context
N/A
Beta Was this translation helpful? Give feedback.
All reactions