Closed vorburger closed 1 year ago
Hm, so I MAY be able to work around this by manually (!) adding all (!) those dependencies to the MODULE.bazel
in my project.
Other than being a (one-time) PITA, even if it works (TBC, WIP), somehow that doesn't feel like the right solution.
Won't such a hard-coded version lead to version skew / mismatch the next time around I upgrade the rules_proto_grpc
version from 4.3.0
to something more recent which requires another proto-google-common-protos
?
Is there a better way to solve this?
adding dependencies to the MODULE.bazel in my project
This seems to do the trick, at least for the classpath of my project:
"com.google.api.grpc:proto-google-common-protos:2.17.0",
"io.grpc:grpc-netty:1.54.1",
"org.apache.tomcat:annotations-api:6.0.53",
Issue Description
I'm attempting to add the
java_grpc_library
as per https://rules-proto-grpc.com/en/latest/lang/java.html#java-grpc-library to an existing project (https://github.com/enola-dev/enola) where I already have thejava_proto_library
(without gRPC) working, and I'm getting build errors due to missing gRPC Java libraries dependencies.It seems that it's not able to find those libraries, but I have not yet been able to figure out what's missing to add them.
Log Output
The exact library missing that the log shows appears to be non-deterministic and varies between different runs; it's one of either
com_google_api_grpc_proto_google_common_protos
:and/or
org_apache_tomcat_annotations_api
as in:rules_proto_grpc Version
4.3.0
Bazel Version
6.1.2
OS
Linux
Link to Demo Repo
https://github.com/enola-dev/enola/pull/125
WORKSPACE Content
BUILD Content
Proto Content
Any Other Content
No response