bazel-contrib / bazel-contrib/rules_scala

Flag --incompatible_disable_depset_items will break rules_scala in a future Bazel release

Open
#905 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

blocked-by-dependency
Dominant language
Starlark
Stars
384
Forks
292
Avg merge
2d 21h
Merged PRs (30d)
46

Description

Incompatible flag --incompatible_disable_depset_items will be enabled by default in a future Bazel release [1], thus breaking rules_scala.

The flag is documented here: https://github.com/bazelbuild/bazel/issues/9017

Please check the following CI builds for build and test results:

Never heard of incompatible flags before? We have documentation that explains everything.

If you don't want to receive any future issues for rules_scala or if you have any questions,
please file an issue in https://github.com/bazelbuild/continuous-integration

Important: Please do NOT modify the issue title since that might break our tools.

[1] The target release hasn't been determined yet. Our tool will update the issue title once the flag flip has been scheduled.

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.

Research direction

Start by reading the linked Bazel issue about --incompatible_disable_depset_items and reviewing the four referenced CI builds. Use their build and test results to locate the affected rules_scala behavior. Done means rules_scala builds and tests successfully when the incompatible flag is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.