aboutsummaryrefslogtreecommitdiff
path: root/java_grpc_library.bzl
AgeCommit message (Collapse)Author
2018-04-26Bazel: Fix compilation in Java 9David Ostrovsky
Fixes: #3633. Test Plan: On most recent Bazel version run: $ bazel --host_javabase=/usr/lib64/jvm/java-9-openjdk \ build --javacopt='--release 9' \ --java_toolchain=@bazel_tools//tools/jdk:toolchain_jdk9 \ examples:helloworld_java_grpc
2018-04-03java_grpc_library: Add support for protobuf liteEric Anderson
gRPC's protobuf-lite auto-selects between full and lite protobuf based on the value of crosstool_top. If the user is specifying their own --android_crosstool_top, then it will not auto-detect correctly. One day, platforms will fix problems like this, but for the moment it seems we get to live with it.
2018-04-03java_grpc_library: re-add grpc-java repo to targetsEric Anderson
They were removed in 137c74d1 since it was believed they were unnecessary. However, since they are in a macro and not a rule, they are relative to the caller, not their definition. Added building the examples to the kokoro CI. Note that this means the examples are built twice: once in grpc-java's build and once in their own (because it has a WORKSPACE). Given that the Bazel build is our fastest build, this slowdown won't probably be an issue.
2018-02-21Drop @grpc_java from labelsCarmi Grushko
These don't contribute if grpc-java is imported with name = grpc_java, and break the build if grpc-java is imported with another name.
2018-01-09bazel: Remove com_google_protobuf_javaRodrigo Queiro
This was deprecated with Bazel 0.8.0, which now uses @com_google_protobuf instead. This change will break users that use grpc_java_repositories(omit_com_google_protobuf_java=True), so I've added a custom error message to make the resolution clearer.
2017-11-06java_grpc_library: fix remote protos that are 'src'sEric Anderson
'includes' were already handled, but not 'src's. This allows you to depend on things like :any_proto from the protobuf repo. Fixes #3650
2017-09-21java_grpc_library.bzl: fix path-manipulation bug.Brendan Linn
_path_ignoring_repository munges bazel filesystem paths into proto import paths, in order to pass to protoc -I. Currently, the function assumes that the include's path begins with the bazel workspace root, which can therefore be sheared off the front of the path. This assumption is incorrect. For an include living in an external repository (say, `@com_google_protobuf//:timestamp_proto`), the filesystem path is something like `bazel-out/darwin_x86_64-fastbuild/genfiles/external/com_google_protobuf/google/protobuf/timestamp.proto`. (See also: http://docs.bazel.build/versions/master/skylark/lib/Label.html#workspace_root.) This commit changes _path_ignoring_repository to handle this case correctly.
2017-08-11all: Fix mismatch in naming Bazel Maven jarsPaul Gross
This commit aligns the naming of the Bazel Maven jars with the names used by Bazel's migration-tooling project: https://github.com/bazelbuild/migration-tooling Unfortunately, we can't fix @com_google_protobuf_java because it's required by Bazel itself. Fixes #3328
2017-06-22build: Add Bazel java_grpc_library ruleSimon Horlick
Bazel third party dependencies are specified in repositories.bzl which gives the consumer the ability to opt-out of any dependencies they use directly in their own project. Fixes #2756