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

[java] Rename of java_names.h -> names.h causes downstream breakages #10069

Closed
jvolkman opened this issue May 27, 2022 · 4 comments
Closed

[java] Rename of java_names.h -> names.h causes downstream breakages #10069

jvolkman opened this issue May 27, 2022 · 4 comments
Assignees

Comments

@jvolkman
Copy link
Contributor

jvolkman commented May 27, 2022

What version of protobuf and what language are you using?
Version: v3.21.0
Language: Java

google/protobuf/compiler/java/java_names.h was renamed to names.h in 40db3da. Ideally there'd be some forwarding header to ease this transition.

See discussion about grpc-java at grpc/grpc-java#9218

Edited by ejona86: Fixed the commit link to reference protobuf instead of grpc PR commit

@ejona86
Copy link
Contributor

ejona86 commented May 27, 2022

Changing the name is fine from our perspective; we don't need the old header long-term. But it would have been good if the first release that included the new name didn't also delete the old one. That is a flag-day that is guaranteed to cause breakages and prevent upgrades.

@deannagarcia
Copy link
Member

I'm sorry this breaking change was unannounced and no transitions were available. The protobuf team is working harder to ensure that breaking changes are intentional and well publicized, and will now follow this policy.

Would forwarding headers still be helpful or has this issue been resolved?

@deannagarcia deannagarcia self-assigned this Jul 12, 2022
@ejona86
Copy link
Contributor

ejona86 commented Jul 18, 2022

gRPC Java has preprocessor logic to fix the build starting in 1.47.0. Most people don't build the grpc java protoc plugin from source, so they aren't impacted either way. I expect this mainly impacted Bazel users. To upgrade to newer Protobuf, those Bazel users would also need to upgrade to newer gRPC.

At this point forwarding includes wouldn't hurt, but I don't know if it'd actually benefit someone.

@deannagarcia
Copy link
Member

Ok I will go ahead and close this bug since I think it's likely people already did the necessary migrations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants