hbase-issues mailing list archives

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

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

Enis Soztutar commented on HBASE-5341:
--------------------------------------

I don't see a reason for changing the release process. The vote for 0.92.0 release included
both the plain and secure artifacts, see http://comments.gmane.org/gmane.comp.java.hadoop.hbase.devel/25671
                
> 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