rules_scala
rules_scala copied to clipboard
bazelbuild
Scala rules for Bazel
One issue is that this means Windows will not respect `runtime_jdk`. Another issue is that we have different code paths for finding the java binary. https://github.com/bazelbuild/rules_scala/blob/cd556ccfc253bfd70659631079e39be412b5402d/scala/private/phases/phase_write_executable.bzl#L83
E.g. from bazel's repo, adding `#` to the end of test filter class would work. ``` % bazel test //src/test/java/net/starlark/java/syntax:all --test_filter=net.starlark.java.syntax.LexerTest INFO: Analyzed 2 targets (0 packages loaded, 0 targets...
I am trying to run scalafmt on all targets using combined bazel run and query: ``` bazel run $(bazel query 'kind("generated file", //...:*)' | grep format-test) ``` But this fails...
Issue #1257 is happening still with modern bazel and rules_scala. ``` $ bazel build @io_bazel_rules_scala//src/java/io/bazel/rulesscala/scalac:scalac.jar 2>&1 | $PAGER ────────────────────────────────────────────────────────────────────────── │ STDIN ────────────────────────────────────────────────────────────────────────── 1 │ INFO: Invocation ID: de2a58ee-4a26-428c-b775-8990ef9c6017 2 │...
`bazel` commands shouldn't print anything on success. Can you suppress or fix these warnings please? ``` # HEAD from 2021-11-29 RULES_SCALA_VERSION = "1d98a8013853b73c825c727be9467e5ea15cc262" RULES_SCALA_SHA = "50963bf5d38dab524bffe941bf5fd68c06de6e6ee75e6b12a8610de7ca409880" http_archive( name = "io_bazel_rules_scala",...
Attach the screenshot in case it got slack log rotated 
I was attempting to see if our Scala code could build under a stricter toolchain as we are currently plagued by over-broad dependency lists and reliance on transitive targets pulling...
these rules were early (the earliest?) adopters of the worker protocol, which uses protobuf, but the proto dependency has caused a lot of issues: #779 #1254 #1305 but recently, bazel...
I have created a minimal repro at https://github.com/bazelbuild/rules_scala/pull/1358/files 3 targets: a -> b -> c. Temporarily setting the following for scala toolchain to show the point. ``` --- a/scala/BUILD +++...
I recently realized that `scala_test_suite` doesn't perform unused dependency checks. I had a look at the code and indeed this is explicitly turned off for both `scala_test_suite` and `scala_library_suite`, with...
