You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/08 19:03:49 UTC

[jira] [Resolved] (HBASE-5341) Push the security 0.92 profile to maven repo

     [ https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-5341.
--------------------------
    Resolution: Won't Fix

Resolving as won't fix. Reopen if I have it wrong. We are a long way from 0.92.

> Push the security 0.92 profile to maven repo
> --------------------------------------------
>
>                 Key: HBASE-5341
>                 URL: https://issues.apache.org/jira/browse/HBASE-5341
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, security
>    Affects Versions: 0.92.1, 0.94.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>            Priority: Blocker
>
> 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. 
> Edit: after some discussion, and the plans for modularizing the build to include a security module, we changed the issue description to push the security jars in 0.92.1 to maven repo. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)