Using maven
as the repo name causes duplicate warnings when using bzlmod
#16839
Labels
untriaged
auto added to all issues by default when created.
maven
as the repo name causes duplicate warnings when using bzlmod
#16839
Downstream bug in rules_jvm_external: bazelbuild/rules_jvm_external#916
What version of protobuf and what language are you using?
v23.1
What did you expect to see
A clean build when using bzlmod.
What did you see instead?
Summarizing @shs96c in bazelbuild/rules_jvm_external#916 (comment)
The common
maven
repo name allows rulesets to contribute to the user's JARs. However, this implies thatmaven
is for the end user, not for transitive dependencies. If a ruleset needs private dependencies, it should use a custom namespace rather than themaven
namespace.maven
.maven
.Proposed fixes
There are a few ways to fix the logline:
maven
toprotobuf_maven
.maven
toprotobuf_maven
.I think 2 is the best short-term option. If you're open to it, I can send a PR.
The text was updated successfully, but these errors were encountered: