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

Dependency upgrades #4700

Closed
elharo opened this issue Jul 30, 2018 · 12 comments · Fixed by #5365
Closed

Dependency upgrades #4700

elharo opened this issue Jul 30, 2018 · 12 comments · Fixed by #5365
Milestone

Comments

@elharo
Copy link
Contributor

elharo commented Jul 30, 2018

In build.gradle

google_api_protos: 'com.google.api.grpc:proto-google-common-protos:1.0.0' --> 1.12.0
com.google.auth:google-auth-library-credentials:0.9.0 to 0.9.1
com.google.code.findbugs:jsr305:3.0.0 to 3.0.2
protobufVersion 3.5.1 --> 3.6.0

There may be others but these are the ones that are conflicting upstream (that is, other versions already being selected) in google-cloud-java

@carl-mastrangelo
Copy link
Contributor

@elharo We can't do the protobuf one because we are still stuck on Java6, and proto requires Java7. I can see about testing the JSR 305 internally, but cannot comment on the auth library. Perhaps @ejona86 can say more.

@ejona86
Copy link
Member

ejona86 commented Jul 30, 2018

Note that #4680 would reduce the need for issues like this, as we could regularly bump all versions.

It looks like proto-google-common-protos is broken, in that it doesn't include the .proto files any more.

We definitely want google-auth-library-credentials bump. It adds JWT caching. It's disappointing we didn't do that earlier. Note that we should actually bump to 0.10.0, not 0.9.1.

jsr305 bump seems like it'd be fine.

A week or so after 1.14.0 release we can drop support of Java 6 and bump the version of protobuf. We can also bump Guava at the same time.

@elharo
Copy link
Contributor Author

elharo commented Jul 31, 2018

@ejona86 Is this the breakage you're referring to? I just saw this at head. If so, I guess that's a separate issue to fix?

> Task :grpc-compiler:compileJava_pluginExecutableJava_pluginCpp
In file included from /Users/elharo/grpc-java/compiler/src/java_plugin/cpp/java_plugin.cpp:8:
/Users/elharo/grpc-java/compiler/src/java_plugin/cpp/java_generator.h:8:10: fatal error: 'google/protobuf/io/zero_copy_stream.h' file not found
#include <google/protobuf/io/zero_copy_stream.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

/Users/elharo/grpc-java/compiler/src/java_plugin/cpp/java_generator.h:8:10: fatal error: 'google/protobuf/io/zero_copy_stream.h' file not found
#include <google/protobuf/io/zero_copy_stream.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

In file included from /Users/elharo/grpc-java/compiler/src/java_plugin/cpp/java_generator.cpp:1:
/Users/elharo/grpc-java/compiler/src/java_plugin/cpp/java_generator.h:8:10: fatal error: 'google/protobuf/io/zero_copy_stream.h' file not found
#include <google/protobuf/io/zero_copy_stream.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

@patflynn
Copy link

@carl-mastrangelo looking at #3961 I don't see any critical reasons to block dropping 6. Am I reading right? Could you consider prioritizing that change? It would be nice to drop Java 6 support across the board for Google libraries. (Java 7 too).

@ejona86
Copy link
Member

ejona86 commented Jul 31, 2018

@elharo, no that's not I was referring to. That's a problem with 1) not having protobuf headers available or 2) having too old a version of protobuf. The problem I was talking about would impact running codegen for .proto files that depend on the generated code in proto-google-common-protos, not compiling codegen.

@patflynn, right now we're just biding our time for a few more people to notice the announcement of dropping Java 6 support that we're going to include in the release today. But #3961 is really the place for discussion on dropping support of Java 6. #4671 is for dropping Java 7.

@elharo
Copy link
Contributor Author

elharo commented Jul 31, 2018

Filed #4715 for the proto issue

@ejona86 ejona86 added this to the Next milestone Aug 7, 2018
@zxtwonder
Copy link

A question about protobuf version - Can grpc-java work with protobuf 3.6.0 currently after overriding dependency? And what is the current plan to officially move to protobuf 3.6.0+?

We have a mixed dependency on protobuf and grpc in C++ and Java. Currently we downgrade to protobuf 3.5.1 across the board to generate universal proto C++ files to accommodate grpc-java.

@ejona86
Copy link
Member

ejona86 commented Nov 12, 2018

grpc-java works with 3.6.0. grpc-java should always work with newer minor/patch versions of dependencies... except for Netty (which is why we have grpc-netty-shaded).

v1.15.0 dropped Java 6 support, and it didn't have any fallout. So starting in v1.16 we could have upgraded the protobuf dependency fairly safely. We just got side-tracked with other things and didn't. It would be nice to do for v1.17...

@elharo
Copy link
Contributor Author

elharo commented Feb 14, 2019

Maybe for 1.19 we can upgrade protobuf?

@elharo
Copy link
Contributor Author

elharo commented Feb 14, 2019

Looks like it's done in build.gradle. Think I saw an example file somewhere that still used the old version though. Searching...

@elharo
Copy link
Contributor Author

elharo commented Feb 14, 2019

all of these are done except google-auth-library-credentials which should now be bumped to 0.12.0

@ejona86
Copy link
Member

ejona86 commented Feb 14, 2019

@elharo, it looks like 0.13.0 is out. That's probably what we'd upgrade to.

ejona86 added a commit to ejona86/grpc-java that referenced this issue Feb 14, 2019
0.13.0 is the latest version.

This honestly doesn't do much since any user of our auth API will be
depending on the library themselves (we only depend on the interface; no
implementation). But getting past 0.9.1 may encourage our users to use a
newer version with better JWT handling and 0.9.1 was released 10 months
ago, so we're overdue for an update.

Fixes grpc#4700
ejona86 added a commit to ejona86/grpc-java that referenced this issue Feb 14, 2019
0.13.0 is the latest version.

This honestly doesn't do much since any user of our auth API will be
depending on the library themselves (we only depend on the interface; no
implementation). But getting past 0.9.1 may encourage our users to use a
newer version with better JWT handling and 0.9.1 was released 10 months
ago, so we're overdue for an update.

Fixes grpc#4700
ejona86 added a commit that referenced this issue Feb 15, 2019
0.13.0 is the latest version.

This honestly doesn't do much since any user of our auth API will be
depending on the library themselves (we only depend on the interface; no
implementation). But getting past 0.9.1 may encourage our users to use a
newer version with better JWT handling and 0.9.1 was released 10 months
ago, so we're overdue for an update.

Fixes #4700
@ejona86 ejona86 modified the milestones: Next, 1.20 Feb 16, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 17, 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 a pull request may close this issue.

5 participants