Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARNING: .../external/grpc-java~/services/BUILD.bazel:107:13: in java_library rule @@grpc-java~//services:reflection: target '@@grpc-java~//services:reflection' depends on deprecated target '@@grpc-proto~//:reflection_java_proto_deprecated': Use :reflection_java_proto instead #11792

Open
vorburger opened this issue Dec 30, 2024 · 1 comment
Milestone

Comments

@vorburger
Copy link
Contributor

What version of gRPC-Java are you using?

bazel_dep(name = "grpc-java", version = 1.69.0, repo_name = "io_grpc_grpc_java")

What did you expect to see?

No Warnings.

What did you see instead?

WARNING: /home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/grpc-java~/services/BUILD.bazel:107:13: in java_library rule @@grpc-java~//services:reflection: target '@@grpc-java~//services:reflection' depends on deprecated target '@@grpc-proto~//:reflection_java_proto_deprecated': Use :reflection_java_proto instead
WARNING: /home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/grpc-java~/services/BUILD.bazel:170:18: in _java_grpc_library rule @@grpc-java~//services:_reflection_java_grpc: target '@@grpc-java~//services:_reflection_java_grpc' depends on deprecated target '@@grpc-proto~//:reflection_proto_deprecated': Use :reflection_proto instead
WARNING: /home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/grpc-java~/services/BUILD.bazel:170:18: in _java_grpc_library rule @@grpc-java~//services:_reflection_java_grpc: target '@@grpc-java~//services:_reflection_java_grpc' depends on deprecated target '@@grpc-proto~//:reflection_java_proto_deprecated': Use :reflection_java_proto instead

Steps to reproduce the bug

TBD.

@kannanjgithub
Copy link
Contributor

This is due to how the service is internally implemented. There is a V1 reflection service that only uses v1 reflection proto. There is the older V1 reflection service that uses v1 alpha (deprecated) reflection proto and internally wraps itself around the newer v1 reflection service.
The only issue is that both services are part of the same Bazel project. We can add a suppress warning for deprecation in bazel.

@kannanjgithub kannanjgithub added this to the Next milestone Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants