[
https://issues.apache.org/jira/browse/HBASE-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954810#comment-13954810
]
Lars Hofhansl commented on HBASE-10847:
---------------------------------------
OK... Here's my "final" proposal.
* Pull security code into the normal build
* Run tests with normal WritableRpcEngine
* All the security tests already configure themselves to run with the
SecureRpcEngine
* Add a TestFromClientSideWithSecureRpcEngine
* _Rename_ the security profile to security-test and keep the secure test
resources
* Keep the -security jenkins build and run it with the secure-test profile
That way we get some test coverage for SecureRpcEngine with just the normal
build, and full coverage for both WritableRpcEngine and SecureRpcEngine among
the two jenkins runs. The default HBase build will ship with all the security
code.
> 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-v3.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)
