bazelbuild / bazelbuild/rules_java
Release the java runfiles library as a maven coordinate
- Dominant language
- Starlark
- Stars
- 103
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
When working on a project that doesn't build with bazel but needs to use the runfiles library (for example, when porting a project from gradle to bazel) there's no easy way to access the java runfiles library. [The Python world exports theirs as a wheel](https://pypi.org/project/bazel-runfiles/).
It would be helpful to expose the java runfiles library as a maven coordinate.
Bazel projects can either not use the coordinate or use a `maven.override` to point to the Bazel-provided version.
Contributor guide
Research direction
Start by locating the Java runfiles library and the repository's existing release configuration. Determine how the library could be published as a Maven coordinate while preserving the Bazel-provided version path, then verify that a non-Bazel consumer can resolve and use the published artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100