bazel-contrib / bazel-contrib/rules_scala
revert #801 after bazel toolchains correctly deal with target dependencies
Open
- Dominant language
- Starlark
- Stars
- 384
- Forks
- 292
- Avg merge
- 3d 3m
- Merged PRs (30d)
- 42
Description
See thread:
https://groups.google.com/forum/#!msg/bazel-discuss/vXrG6uFL5V8/RjK8_chaEgAJ
and the change we had to do on #801 to deal with it.
cc @katre @ianoc
Contributor guide
Research direction
Start by reading issue #801 and the linked bazel-discuss thread to understand the target-dependency problem and the change made in response. Identify the files changed by #801, then determine whether those changes can be reverted now that Bazel toolchains correctly handle target dependencies. Done means the unnecessary workaround from #801 is reverted without breaking the Scala rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100