[
https://issues.apache.org/jira/browse/HBASE-18855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174236#comment-16174236
]
stack commented on HBASE-18855:
-------------------------------
Sure. The current route is well-trod. It is what netty community made so folks
could shade and have their own .so. It is a bit of a pain, yeah, but
netty-provided so will probably work a while over upgrades, etc.
Waiting on a patch.
Why is this 'maybe' improvement marked as critical?
Good on you [~mdrob]
> rewrite netty so to have proper packages
> ----------------------------------------
>
> Key: HBASE-18855
> URL: https://issues.apache.org/jira/browse/HBASE-18855
> Project: HBase
> Issue Type: Improvement
> Components: thirdparty
> Reporter: Mike Drob
> Priority: Critical
>
> We documented the workaround for folks using surefire needing to set a system
> property otherwise mini cluster won't start in HBASE-18849, but maybe we can
> do better.
> Can we rewrite the SO? Or patch the java code to use the correct value
> instead of checking a system property for it? It should be ok to have a patch
> to hardcode this sine we're telling folks to use a static value anyway.
> hbase-thirdparty already has mechanisms for patching the source libs (ref.
> protobuf) so the mechanics shouldn't be too complex.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
