Skip to content

Conversation

@drigz
Copy link
Contributor

@drigz drigz commented Jan 7, 2019

This makes grpc-java compatible with recent Bazel releases by pulling
in changes including:

protocolbuffers/protobuf#4650
protocolbuffers/protobuf@c2f88de

Is it OK to update the Bazel dependency separately, or should I update references, as in #3921?

This makes grpc-java compatible with recent Bazel releases by pulling
in changes including:

protocolbuffers/protobuf#4650
protocolbuffers/protobuf@c2f88de
@ejona86
Copy link
Member

ejona86 commented Jan 14, 2019

@drigz, sorry for the late reply. Go ahead and update all references of protobuf to the 3.6.1 release (like in the other PR you mentioned). It's safe since gRPC dropped support for Java 6 (#3961).

In the past updating protobuf version has been a bit of a pain because of compiler warnings. If it becomes too painful for you just tell us and we will work on bumping the version.

@drigz
Copy link
Contributor Author

drigz commented Jan 15, 2019

@ejona86 I gave it a shot, but it seems quite involved - especially because protobuf dropped support for javanano (source). Should I file an issue for the update and close this PR?

@ejona86
Copy link
Member

ejona86 commented Jan 15, 2019

@drigz, oh, you leave javanano in the past. Sorry for the confusion. We can take it from here. Let's leave this open until we make a replacement PR.

@ejona86
Copy link
Member

ejona86 commented Feb 5, 2019

Closing in favor of #5320

@ejona86 ejona86 closed this Feb 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants