Publish embedded tools in `bazel_tools` as their own modules
Open
P2
team-OSS
type: feature request
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 75
Description
Context: https://github.com/bazelbuild/bazel/pull/28428#issuecomment-3800463838
This could include:
- proto files
- C++ binary launcher
- ijar?
- repo rules??
Contributor guide
Research direction
Start with the bazel_tools entry point and read the discussion in PR #28428, especially the linked issue comment. Clarify which embedded tools are in scope—proto files, the C++ binary launcher, ijar, and repository rules—and define the module boundaries before implementation. Done means the agreed tools are published as their own modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100