Add a bzlmod extension to override default repositories about rules_jvm_external HOT 2 CLOSED

You don't need to do this. All you need to do in your root module is to add a maven.install(name = "workspace-name-to-override", repositories = [...])

You can also use the downloader config option to rewrite remote requests. This "things download from unexpected places" problem is exactly what it was designed to solve.

from rules_jvm_external.

You don't need to do this. All you need to do in your root module is to add a maven.install(name = "workspace-name-to-override", repositories = [...])

You can also use the downloader config option to rewrite remote requests. This "things download from unexpected places" problem is exactly what it was designed to solve.

The problem with the maven install is that with various tools usage (openapi generator, libraries for tests which run independently with rules_itest, etc), I'm isolating them from each other and from the "production" code that lives in the monorepo.

I currently have 3 different maven.install and soon to be more where I have to repeat the same repository setting instead of having this set globally for all of them.

The downloader config option is one thing but while it looks like a valid option I find it rather non-obvious where your artifacts are coming from when you look at the MODULE.bazel file and you need to know that bazel as such "override" mechanism. Imo, not a great DX. It does address the point for rules that don't have such an override mechanism directly in MODULE.bazel though or the language specific configs.

from rules_jvm_external.