-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
all: Update netty to 4.1.77.Final and netty_tcnative to 2.0.53.Final #9027
Conversation
263f128
to
4ffb3cb
Compare
711238b
to
ce8b750
Compare
e325ab0
to
ba76107
Compare
examples/example-tls/pom.xml
Outdated
@@ -57,6 +57,12 @@ | |||
<version>${netty.tcnative.version}</version> | |||
<scope>runtime</scope> | |||
</dependency> | |||
<dependency> | |||
<groupId>io.netty</groupId> | |||
<artifactId>netty-tcnative-classes</artifactId> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd expect this not to be necessary for Maven. Remove this dependency?
Although, actually, I see you didn't update the build.gradle for this example. It is using grpc-netty-shaded. We should swap to using grpc-netty-shaded here and then we don't need to define netty-tcnative at all. I've tested that works without issue.
…rpc#9027) all: Update netty to 4.1.77.Final and netty_tcnative to 2.0.53.Final Also switches to a non-release version of rules_jvm_external to allow Bazel build to work with artifact classifiers.
This is a more complicated Netty upgrade as netty-tcnative was split into:
netty-tcnative-classes
that has all the Java codenetty-tcnative-boringssl-static
that no longer has all of the native libraries, but instead declares dependencies to itself with a platform specific Maven classifiers (e.g.linux-x86_64
)This causes problems for:
This PR includes direct dependencies to
netty-tcnative-boringssl-static
with all the platform classifiers.The latest Bazel release also has a problem with using platform classifiers. This PR changes to use a non-released version of rules_jvm_external that has a fix to the problem (bazel-contrib/rules_jvm_external#687).