[
https://issues.apache.org/jira/browse/HBASE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954470#comment-13954470
]
Lars Hofhansl commented on HBASE-10847:
---------------------------------------
I think that'd be for another ticket with more discussion. Now sure - now
thinking about it more - if folks would rely on anything specific from
WritableRcpEngine.
For this ticket I'd like to:
# Default to the secure build, but with WritableRpcEngine still by default
# Get rid of the secure jenkins build, run all tests including the secure ones
as part of one run
# Allow the secure artifacts in maven
The sticky part is the testing as mentioned above. If we do not want to run two
full builds anymore we'll have to accept decreased coverage for one of the Rpc
Egnines. Many tests do not use RPC anyway. So I think it might be best to
switch to SecureRpcEngine for tests now and run TestFromClientSide and
TestTableInputFormat (and others?) with both Rpc Engines.
> 0.94: drop non-secure builds, make security the default
> -------------------------------------------------------
>
> Key: HBASE-10847
> URL: https://issues.apache.org/jira/browse/HBASE-10847
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.19
>
> Attachments: 10847-v2.txt, 10847.txt
>
>
> I would like to only create a single 0.94 tarball/release that contains the
> security code - and drop the non-secure tarballs and releases.
> Let's discuss...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
