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] Provide a migration guide for the breaking changes introduced in 26.0 #17000

Closed
blakeli0 opened this issue May 31, 2024 · 2 comments
Closed
Labels
inactive Denotes the issue/PR has not seen activity in the last 90 days. java

Comments

@blakeli0
Copy link

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

Describe the problem you are trying to solve.

Protocol Buffers v26.0 introduced a lot of breaking changes for Java. To prepare for the upgrade, we are trying to replace the usage of all the removed methods before the upgrade. However, there is no official migration guide for v26.0, and it's usually not easy to find direct replacements for the removed methods either due to lack of Javadoc.
For example, OneofDescriptor.isSynthetic() was deprecated and now de-scoped, but there was no Javadoc or release notes hinting for a direct replacement. We tried our best to fix it in googleapis/sdk-platform-java#2764 by reading the source code, but we are not 100% confident and it would be great if there is something official for us to follow.

What we are asking for is an official guide that provides direct replacements or alternatives for all the removed methods. There is already an issue #16452 asking for a migrating path, but that issue is more for projects without a direct Protobuf dependency, focused on resolving runtime issues. This issue is more for projects with a direct Prorobuf dependency, and focused on compilation issues.

@blakeli0 blakeli0 added the untriaged auto added to all issues by default when created. label May 31, 2024
@acozzette acozzette added java and removed untriaged auto added to all issues by default when created. labels Jun 4, 2024
Copy link

github-actions bot commented Sep 3, 2024

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please add a comment.

This issue is labeled inactive because the last activity was over 90 days ago. This issue will be closed and archived after 14 additional days without activity.

@github-actions github-actions bot added the inactive Denotes the issue/PR has not seen activity in the last 90 days. label Sep 3, 2024
Copy link

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please reopen it.

This issue was closed and archived because there has been no new activity in the 14 days since the inactive label was added.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Denotes the issue/PR has not seen activity in the last 90 days. java
Projects
None yet
Development

No branches or pull requests

2 participants