bazel-contrib / bazel-contrib/rules_jvm
Duplicate artifacts versions
- Dominant language
- Go
- Stars
- 54
- Forks
- 98
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 7
Description
Upon using the `contrib_rules_jvm` and the `rules_jvm_external` in my project, I get the following warning:
```
DEBUG: /home/zshaban/.cache/bazel/_bazel_zshaban/31dd816ecc4dd5f7e9765c5f08aebaf2/external/rules_jvm_external~5.3/coursier.bzl:597:18: Found duplicate artifact versions
com.google.errorprone:error_prone_annotations has multiple versions 2.11.0, 2.9.0
com.google.guava:guava has multiple versions 30.1.1-jre, 31.0.1-android
```
Since those duplicate versions are explicitly mentioned in the `MODULE.bazel` of the `contrib_rules_jvm`, would it make sense to set `duplicate_version_warning = "none"` in the maven extension used in the `contrib_rules_jvm`?
Contributor guide
Research direction
Read the contrib_rules_jvm MODULE.bazel and the Maven extension configuration referenced by the issue, then reproduce the warning with both extensions enabled. Check how duplicate_version_warning is handled for the explicitly listed versions; done when the intended behavior is confirmed and the resulting warning behavior is covered by an appropriate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100