[
https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201928#comment-13201928
]
Zhihong Yu commented on HBASE-5341:
-----------------------------------
If you search for the voting process by entering the following in
http://search-hadoop.com:
'ANN: The fifth hbase 0.92.0 release candidate is available for download'
one can hardly tell whether the voters tested with secure hbase tar ball.
If we produce one artifact (I think we should), some voters have to test
security features before we declare new release.
> HBase build artifact should include security code by defult
> ------------------------------------------------------------
>
> Key: HBASE-5341
> URL: https://issues.apache.org/jira/browse/HBASE-5341
> Project: HBase
> Issue Type: Improvement
> Components: build, security
> Affects Versions: 0.94.0, 0.92.1
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
>
> Hbase 0.92.0 was released with two artifacts, plain and security. The
> security code is built with -Psecurity. There are two tarballs, but only the
> plain jar in maven repo at repository.a.o.
> I see no reason to do a separate artifact for the security related code,
> since 0.92 already depends on secure Hadoop 1.0.0, and all of the security
> related code is not loaded by default. In this issue, I propose, we merge the
> code under /security to src/ and remove the maven profile.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
