bazel-contrib / bazel-contrib/rules_jvm_external
Fallback to standard folder structure for resolution / artifact download when POM file is missing
- Dominant language
- Java
- Stars
- 373
- Forks
- 301
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 3
Description
Context :
While most artifact on public repo contain artifact automatically generated (i.e including a POM file by default), private repo have their artifact manually uploaded, without the corresponding POM file. This is not a good practice, however other build system (gradle) seems to fallback in this case and download/use the artifact JAR/AAR anyway (if present) and assume no dependencies.
Request/Suggestion:
Follow the same mechanism. It will help companies using their own artifact servers, when proper POM file uploads have been neglected.
Contributor guide
Research direction
The issue identifies resolution and artifact-download behavior, with JAR/AAR fallback when a POM is absent. Start by locating those paths and their existing tests; done means an artifact without a POM resolves and downloads successfully while being treated as having no dependencies.
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
- 25/100