[
https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202103#comment-13202103
]
stack commented on HBASE-5341:
------------------------------
bq. This would break the ability to compile HBase 0.92+ against Hadoop releases
without security.
Perhaps we could entertain breaking this for 0.94.0? i.e. saying we only run
on hadoops w/ security? (CDH3 has it? What doesn't that we want to run on by
the time 0.94.0 is out).
On modularization, yes, if hbase-4336 is done soon, security is a natural.
Otherwise, we should do as Enis suggests.
> 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
