rules_scala
rules_scala copied to clipboard
bazelbuild
Scala rules for Bazel
So, I met with @cgrushko a few days ago and apparently the way we (rules_scala) currently do strict deps (allowing a target to only use what it directly depends on)...
Whenever the compilation action has diagnostics support, as it is currently being handled in https://github.com/bazelbuild/bazel/pull/11766, that argument for the diagnostics file should be properly passed for that version of bazel...
Resolves to https://github.com/bazelbuild/rules_scala/issues/877 Step 0: Generate sig jars for scala_library
With precompiled libraries java_* rules put the library on java.library.path. scala_* rules currently do not.
https://github.com/seanmcl/scala-bazel-bug-linker demonstrates a bug that shows java.library.path is not set correctly. I haven't found a workaround for this. No combination of DYLD_LIBRARY_PATH, --test_env, --action_env, --jvmargs lets me set the path,...
There is a section in the README that states we should add ``` skylib_version = "1.0.3" http_archive( name = "bazel_skylib", sha256 = "1c531376ac7e5a180e0237938a2536de0c54d93f5c278634818e0efc952dd56c", type = "tar.gz", url = "https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/{}/bazel-skylib-{}.tar.gz".format(skylib_version, skylib_version),...
I'm not sure if my title makes sense, but let me explain: I have a proto that imports `"google/protobuf/timestamp.proto"` and uses it as part of a message. So it all...
I'm using `scala_proto_library` to create a JAR file with the compiled generated protobuf code. However, because this JAR is being consumed by other project that use Maven/Gradle as build system,...
## What? Adds a new rule for compiling protobuf to scala. This rule is not aspect based and that allows the user to add extra dependencies to the compilation. ##...
Following up #825 - after it will get merged - we will probably need to come up with out deprecation policy. It can be separate doc or combined into the...
