hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5341) HBase build artifact should include security code by defult
Date Tue, 07 Feb 2012 05:42:59 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202091#comment-13202091
] 

Gary Helmling commented on HBASE-5341:
--------------------------------------

This would break the ability to compile HBase 0.92+ against Hadoop releases without security.
 Even though we currently compile against 1.0 by default, we haven't block the ability to
compile against previous versions.  So this would be a change, especially if there's anyone
out there running on builds of the 0.20-append branch.

We've also been discussing moving in the direction of a modular build (see HBASE-4336).  The
current security/ tree is practically a module already, just lacking it's own pom.xml.  Moving
security/ back up into src/ would be a step back into the opposite direction, keeping us with
a monolithic release.  This may make the packaging slightly simpler, but it still won't make
it any easier to test out all the combinations of optional components.  The security profile
does currently use it's own configuration for testing, so at least we get execution of the
full test suite using {{SecureRpcEngine}}.  The full test suite is really overkill for testing.
 We could use just a good set of RPC focused tests if we had them.  But in my opinion that
kind of focused testing would be easier to handle in a security module than are part of a
monolithic build.
                
> 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

        

Mime
View raw message