(chores) camel-grpc: fix version conflict causing CI failures #6283
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reordering of the Netty dependencies from b8ca24e is bringing a newer version of the io.netty:netty-tcnative-boringssl-static (2.0.44.Final). Forcing the camel-grpc to use the older one (2.0.39.Final) causes a failure because the class AsyncSSLPrivateKeyMethod is not present on the older one. This causes the GrpcProducerSecurityTest test to fail.
Contributor
Author
|
@jamesnetherton does this look OK to you? |
oscerd
approved these changes
Oct 15, 2021
jamesnetherton
approved these changes
Oct 15, 2021
davsclaus
approved these changes
Oct 15, 2021
Contributor
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The reordering of the Netty dependencies from
b8ca24e is bringing a newer version of
the io.netty:netty-tcnative-boringssl-static (2.0.44.Final). Forcing the
camel-grpc to use the older one (2.0.39.Final) causes a failure because the class
AsyncSSLPrivateKeyMethod is not present on the older one.
This causes the GrpcProducerSecurityTest test to fail.
This should fix the grpc tests on CI