bazel-contrib / bazel-contrib/rules_scala
Cross building
- Dominant language
- Starlark
- Stars
- 384
- Forks
- 292
- Avg merge
- 3d 3m
- Merged PRs (30d)
- 42
Description
So this isn't anything urgent but popped into my head and thought it would be best to start the conversation now before 2.12 is released and we might have more pressure.
2 questions:
1. How to parameterize the rule with respect to scala version? (don't think it's complicated but haven't looked into it).
2. How to cross build a target to both 2.11 and 2.12 like sbt supports. This is useful for both rolling out the upgrade in an organization and for OSS libraries.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's existing Scala rules and how Bazel targets select Scala versions, then compare the requested behavior with sbt's cross-building model. Done should mean targets can be parameterized and built for both Scala 2.11 and 2.12.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100