hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4336) Convert source tree into maven modules
Date Wed, 21 Sep 2011 22:46:26 GMT

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

Jesse Yates commented on HBASE-4336:
------------------------------------

Updated ticket on RB based on Andrew's comments - now its just the poms for each of the packages.

Modules:
hbase (top level)
hbase-core
hbase-server
hbase-security
hbase-it

-security and  -sever poms are essentially empty since I haven't moved over the code yet,
but they should be pretty easy to handle.

I wanted to get an OK on the package structure before doing the code port, but it shouldn't
be too hard (just annoying to make sure I have the right dependencies).

The other thing I was thinking about was where we wanted to build the project. Right now it
drops all the packages into hbase-core/target. Do we want to keep it that way, where the jars
are in the /target for each, or do we want to also copy everything up to hbase/___?

> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message