[
https://issues.apache.org/jira/browse/HBASE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251737#comment-13251737
]
Jesse Yates commented on HBASE-4336:
------------------------------------
bq. I'm excited about this one. I liked the notion by Mat Corgan that we'd have
an hbase-hregion module and then there'd be an hbase-wal so Li Pi can
experiment standalone w/ multiple WALs at the one time, etc., etc. The new
client would be one.....
Yeah, its gonna be great!
bq. Or not. Just do hbase-common and hbase-security? Can roll hbase-security
back into common when time comes.
I'm leaning towards this - no assurances as to when security is going to be
rolled in and its really not a big deal to get rid of the module (and even not
that much pain for people with patches when it is as they just apply the
patches to a new root). Is that the right ticket number for rolling security
in? Doesn't seem directly applicable...
> Convert source tree into maven modules
> --------------------------------------
>
> Key: HBASE-4336
> URL: https://issues.apache.org/jira/browse/HBASE-4336
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Gary Helmling
> Priority: Critical
> Fix For: 0.96.0
>
>
> When we originally converted the build to maven we had a single "core" module
> defined, but later reverted this to a module-less build for the sake of
> simplicity.
> It now looks like it's time to re-address this, as we have an actual need for
> modules to:
> * provide a trimmed down "client" library that applications can make use of
> * more cleanly support building against different versions of Hadoop, in
> place of some of the reflection machinations currently required
> * incorporate the secure RPC engine that depends on some secure Hadoop classes
> I propose we start simply by refactoring into two initial modules:
> * core - common classes and utilities, and client-side code and interfaces
> * server - master and region server implementations and supporting code
> This would also lay the groundwork for incorporating the HBase security
> features that have been developed. Once the module structure is in place,
> security-related features could then be incorporated into a third module --
> "security" -- after normal review and approval. The security module could
> then depend on secure Hadoop, without modifying the dependencies of the rest
> of the HBase code.
--
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
