hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5341) Push the security 0.92 profile to maven repo
Date Wed, 29 Aug 2012 21:56:08 GMT

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

stack commented on HBASE-5341:
------------------------------

Ian

The change has been done in trunk -- there is one artifact only now rather than one for insecure
(?) and another for secure.  I was keeping this issue around as reminder that on release of
next 0.92/0.94 versions, that we'd be sure to put the -security bundle too as Enis suggests
(It might not be possible given dumb mvn release tool but I was going to try it next time
around).  So this issue is a knot on my finger.  Would you like me to make an actual knot
on my finger or would you like me open a more specific issue instead?
                
> 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
>             Fix For: 0.92.3
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message