[
https://issues.apache.org/jira/browse/HBASE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-5341:
---------------------------------
Description:
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.
was:
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.
Summary: Push the security 0.92 profile to maven repo (was: HBase
build artifact should include security code by defult )
I have recycled this issue, and changed the title.
> 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.94.0, 0.92.1
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.92.1
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
