Renovate should also propose version bump updates to Bazel rules_jvm_external maven_install() even if it found a Maven pom.xml

[vorburger]

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

enola-dev/enola#948 is an example of a Renovate proposed version bump to a pom.xml.

The thing is, I was crazy enough 🤣 to have BOTH a Maven pom.xml AND a Bazel based build, in that project...

... so, in an ideal perfect world, I would like Renovate to automagically propose https://github.com/enola-dev/enola/pull/961/files (which I have manually created).

I may remove that pom.xml in enola-dev/enola#966 to see if that helps to unconfuse Renovate. But, in an ideal perfect world, I would hope that I wouldn't have to - why not support bumping dependencies of several build systems in a single repo!

@rarkins FYI

Logs (if relevant)

No response

[github-actions[bot]]

Hi there,

This is intended as a polite, automated request that users avoid @ mentioning repository maintainers like @rarkins or @viceice. Doing so causes annoying mobile notifications and makes it harder to maintain this repository.

We know it might be common elsewhere but we participate in hundreds of discussions a week and would need to turn off GitHub mobile notifications if we were mentioned in every one.

As a general rule, we will read and respond to all discussions in this repository, so there is no need to mention us.

Thanks, the Renovate team

[github-actions[bot]]

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:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[rarkins]

Does renovate detect both dependencies and update both independently? Ie is this just a matter of grouping?

[vorburger]

Does renovate detect both dependencies and update both independently? Ie is this just a matter of grouping?

Actually... I have now further analyzed & thought this through, and I suspect that I made a "logical deduction reasoning" 🤣 mistake:

So on the https://github.com/enola-dev/enola/ repo, from there start I never got any renovates to bump Bazel rules_jvm_external maven_install() deps. That repo uses Bazel since the start, and I've added a pom.xml half way through - but it had never worked BEFORE either.

So the problem in that repo may not that Renovate does not propose bumps to both Bazel and Maven Java deps, but that in that repo Bazel deps bumps just don't work at all.

@rarkins is there any that we could debug why Renovate simply ignoring bumping Bazel Java deps on enola-dev/enola#73 ? What logs from where could I help provide, if any?