[
https://issues.apache.org/jira/browse/RATIS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672339#comment-16672339
]
ASF GitHub Bot commented on RATIS-383:
--------------------------------------
joshelser commented on issue #1: RATIS-383. Shade native library tcnative for
grpc/netty in Ratis-Thir…
URL:
https://github.com/apache/incubator-ratis-thirdparty/pull/1#issuecomment-435216043
> What this patch does is to add the ratis-thirdparty prefix the jar and
native libraries so that they linked properly.
How can we tell if this is working? Can we write a test in ratis-thirdparty
to show this is working as-expected?
For the other changes, we would verify thirdparty is good based on the
ability to build+test the core Ratis build. If we have something manual to run
in the core of Ratis to validate this change, that's OK too.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Shade native library tcnative for grpc/netty in Ratis-Thirdparty
> ----------------------------------------------------------------
>
> Key: RATIS-383
> URL: https://issues.apache.org/jira/browse/RATIS-383
> Project: Ratis
> Issue Type: Bug
> Components: security
> Reporter: Mukul Kumar Singh
> Assignee: Xiaoyu Yao
> Priority: Major
> Labels: ozone
> Attachments: RATIS-383.001.patch
>
>
> RATIS-246 discusses making GRPC endpoint secure with mTLS. This jira is
> needed as GRPC/netty has dependency on tcnative jar/libraries that need to be
> shaded in Ratis-Thirdparty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
