rules_scala
rules_scala copied to clipboard
bazelbuild
Scala rules for Bazel
### Description One step towards Scala 3 Dependency Analyzer: * skeleton implementation of unused dependency checking copied from Dependency Analyzer 2 * test utilities use plugin in compilation pipeline ###...
…utput ### Description Add a new function that is independent of runtime jars and the specific output. ### Motivation This is a small refactoring as an intermediate step for possible...
If I run coverage while using Java 17 it fails with an error: ``` Discovery starting. Discovery completed in 87 milliseconds. Run starting. Expected test count is: 1 TestSuite: things...
While chasing another weird dependency issue, I followed the [docs](https://github.com/bazelbuild/rules_scala/blob/master/docs/dependency-tracking.md) and enabled option B of the dependencies by setting the following flags on the tool chain: ``` dependency_mode = "plus-one",...
grpc version is outdated and can cause issues during build since it is hard to exclude packages from rules_scala rules.
[](https://renovatebot.com) Welcome to [Renovate](https://togithub.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request....
Repro: https://github.com/sjoerdvisscher/bazel-scala-tests `bazel coverage //... --instrumentation_filter=-java` removes java, but `bazel coverage //... --instrumentation_filter=-scala` has scala Repro also demonstrates #1101 Thanks @sjoerdvisscher for reporting
Problem ====== https://github.com/bazelbuild/rules_scala/blob/7a2c3510cda8cf544f9ce9a621a69ac5fe31ae7e/jmh/jmh.bzl#L32 indicates that the expectation is only one jar should be provided in the `info.outputs.jars`, but when writing benchmarks in java and using `scala_benchmark_jmh` directly the attempt at...
i.e. like `java_binary` and `java_test`. One example is how `scala_tests` don't have the `env` attribute from `java_test`. I believe that Bazel inherits attributes by depending on their "parent" classes(?) when...
Seeing some strange behavior when upgrading to Bazel 5 for a mid-sized Scala project I'm looking at. The first issue we worked through was missing classes, and appeared after moving...
