Release the java runfiles library as a maven coordinate

Open
#360 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
build-system, release

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.

Description

P4

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.

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.

Dominant language
Starlark
Stars
103
Forks
102
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bazelbuild/rules_java

All issues in bazelbuild/rules_java

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.