Next week I'm merging a huge PR which effectively rewrites rule.
It has ben under review for 2 months and we've ran it through severa very large codebases (Wix's ~10MLOC passes with it) but I'd still suggest other companies to take it out for a spin and report on the PR bazelbuild/rules_scala#865.
On a related note I'll say that I'm not really looking here and I've moved to bazelbuild slack's org (#scala) so you're invited there as well.
scala_library) currently doesn't add transitive dependencies to compile classpath? (the way java rules does with
--strict_java_deps=off) indicated here: bazelbuild/rules_scala#235
Hey folks - trying to use bazel for a demo project (on my personal dev machine not behind some corporate firewall). this is the error i get
ERROR: /home/ptandel/.cache/bazel/_bazel_ptandel/1dcc102f10d8db6f292e788f608253ba/external/io_bazel_rules_scala/scala/scala.bzl:561:5: //external:io_bazel_rules_scala/dependency/scala/scala_reflect depends on @io_bazel_rules_scala_scala_reflect//:io_bazel_rules_scala_scala_reflect in repository @io_bazel_rules_scala_scala_reflect which failed to fetch. no such package '@io_bazel_rules_scala_scala_reflect//': java.io.IOException: Error downloading [http://central.maven.org/maven2/org/scala-lang/scala-reflect/2.11.12/scala-reflect-2.11.12.jar] to /home/ptandel/.cache/bazel/_bazel_ptandel/1dcc102f10d8db6f292e788f608253ba/external/io_bazel_rules_scala_scala_reflect/scala-reflect-2.11.12.jar: Unknown host: central.maven.org
IIRC central.maven.org doesn't seem to be valid but i couldn't figure out how to specify something else (short of using a HTTP(S) proxy which I'm not sure would solve my problem)?
Hi. I am using IntelliJ, Scala, and the Bazel plugin. I am noticing that some dependencies are not resolved, leading to red font in the code window. The project builds fine from the command line however.
In particular, I've noticed that the
.ijwb/.idea/libraries/ directory is missing an entry for
com.typesafe.configdependency. It doesn't make sense to me because it's explicitly depended upon in my BUILD file (e.g.
deps = [ "//3rdparty/jvm/com/typesafe:config" ]).
Sorry about newbie question.
Where I can find sha256 for selecting scala version in WORKSPACE file?
scala_proto_librarycall uses a custom toolchain? The docs just say "To configure ScalaPB options, configure a different scala_proto_toolchain and declare it in a BUILD file". Any build file? Every build file that needs it?
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.22.0</version> <configuration> <parallel>methods</parallel> <useUnlimitedThreads>true</useUnlimitedThreads> </configuration> </plugin>
@ittaiz @johnynek I have one more question, in order for the targets to be executed in parallel, do I need to have a main build file which calls them?
filegroup( name = "build_all", srcs = [ "//services/service1:build", "//services/service2:build", "//services/service3:build", ] )
Will doing it like this make the execution sequential instead of parallel?
Btw. Don’t know the stage you’re in but if you’re in an initial I recommend you take a look at exodus which is a project aimed at migrating maven projects to fine grain bazel targets. We (Wix) used it to migrate ~10MLOC
Amazing! Well, most of the things have been migrated, however, there are still some that haven't been, so this will come handy, I started looking into it yesterday :)
Hello, I'm getting a bit weird error when defining custom dependencies with scala_proto. I've followed the docs at https://github.com/bazelbuild/rules_scala/blob/master/docs/scala_proto_library.md I've added the
default_deps_toolchain but I'm getting error
File "/private/var/tmp/_bazel_hrvolap/cbad7e6dac15bf07632f0b5b890ca227/external/io_bazel_rules_scala/scala/private/toolchain_deps/toolchain_deps.bzl", line 13, column 9, in _lookup_provider_by_id fail(_required_deps_id_message(ctx.attr.name, toolchain_type_label, deps_id)) Error in fail: scalapb_worker_deps requires mapping of scalapb_worker_deps provider id on the toolchain @io_bazel_rules_scala//scala_proto:deps_toolchain_type
which seems like needs to be added to toolchain, but when I added it as a dep_provider to the
default_deps_toolchain I get dependency cycle.
Also the whole story why I want custom dependencies because grpc client dependency is overlapping with dependencies for bigtable and version are not compatible
I've redefined in my workspace
declare_deps_provider( name = "scalapb_worker_deps_provider", deps_id = "scalapb_worker_deps", visibility = ["//visibility:public"], deps = [ "@com_google_protobuf//:protobuf_java", "//third_party/jvm/com/thesamet/scalapb:protoc_bridge", "//third_party/jvm/com/thesamet/scalapb:compilerplugin", ], )
and included it in default_deps_toolchain, then everything worked