Support for maven_install.json in Bazel Maven Manager #20721
Replies: 4 comments 6 replies
-
|
This would require bazel to be first added to containerbase so that it can be installed: https://github.com/containerbase/base Before that, do projects define a specific version of bazel they support, or should Renovate just install the latest version every time? |
Beta Was this translation helpful? Give feedback.
-
|
Blocked by containerbase/base#20 |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, Please help this Discussion progress 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.
-
|
Hi there, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Type of discussion.
Bug report, the issue template states to create a discussion first
Tell us more.
Hey folks at Renovate,
The new support for Maven dependencies managed by Bazel in Renovatebot is awesome, and our Github repo is now actively receiving PRs from Renovatebot with updates to JVM dependencies.
There's just one problem though that's unfortunately making it not very useful right now: it seems that Renovatebot doesn't support updating
maven_install.json, meaning it doesn't work correctly on any project where Maven artifacts are pinned (you can think of this file as similar topackage-lock.json). Renovatebot simply updates just the artifact declaration inWORKSPACEand doesn't actually re-pin artifacts, which means that dependencies don't actually get updated — as mentioned in the docs, updating the list of artifacts won't affect the build if amaven_install.jsonfile is present:Luckily the solution is straightforward, as it just requires running
REPIN=1 bazel run @unpinned_maven//:pinin the workspace after updating the list of artifacts, which should automatically updatemaven_install.json.I hope it'll be possible for the team to take a look at this! Seems like @zharinov and @rarkins are the experts on this area.
Beta Was this translation helpful? Give feedback.
All reactions