bazel-contrib / bazel-contrib/rules_jvm_external
Can you limit a repository to only certain artifacts?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 373
- Forks
- 301
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 3
Description
We have one weird artifact that lives in its own repository. If we add its repository to the overall repositories field, then that shows up as a mirror URL for every artifact in the project, and Bazel queries it for every other artifact, and users get tons of 404 warnings.
Is there a way to provide repositories per-artifact while staying under the same connected external repository?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the repositories field is applied during Bazel artifact resolution and why it becomes a mirror URL for every artifact. Determine how per-artifact repository configuration could remain within the connected external repository, then verify that unrelated artifacts no longer produce repository 404 warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100