Fix builders ABI backward compatibility broken in v1.33.0 #7564
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What's this PR do?
Brings back
io.grpc.internal.AbstractManagedChannelImplBuilderandio.grpc.internal.AbstractServerImplBuilderto the class hierarchy to fix broken ABI backward compatibility.Any background context you want to provide?
AbstractManagedChannelImplBuilder
AbstractManagedChannelImplBuilderbrought back as a copy ofForwardingChannelBuildersupport pre-v1.33 binary interface, e.g.io.grpc.netty.NettyChannelBuilder.maxInboundMessageSize(I)Lio/grpc/internal/AbstractManagedChannelImplBuilder;AbstractServerImplBuilder
io.grpc.internal.AbstractManagedChannelImplBuilderandio.grpc.internal.AbstractServerImplBuilderto the class hierarchy to fix broken ABI backward compatibility.ForwardingServerBuilderwas introduced in v1.33.0, I changed it toForwardingServerBuilder<T extends ServerBuilder<T>>. and made it package-private.What are the relevant tickets?