bazel-contrib / bazel-contrib/rules_scala
Consider splitting off rules core to building and and testing scala from those that arent
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 384
- Forks
- 292
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 46
Description
We've been bit a few times on upgrade paths due to transient dependencies of rules within this repo I feel are not core to scala support.
Specifically protobuf dependencies are always hard for us to manage.
This could be remedied by keeping rules like scala library in a repo separate from aux rules like thrift, scalapb etc.
I understand this introduces a burden on maintainers but the reward for users feels worth it.
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
The issue names no files, tests, or entry points. Start by mapping the repository's rules and their transient dependencies, focusing on protobuf and the distinction between scala library support and auxiliary rules such as thrift and scalapb. Done would require an agreed maintainable split that reduces upgrade-path dependency burden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100