Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 21 Sep 2011 22:46:26 +0000 (UTC)
From: "Mikhail Bautin (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1213026491.222.1316645186956.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1723720443.22663.1315348870618.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4336) Convert source tree into maven
 modules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mikhail Bautin commented on HBASE-4336:
---------------------------------------

Is it possible to split the existing set of packages between multiple jars without touching every file in the source directory? We have a lot of patches queued up for open-sourcing in the near term, and moving every file around would make it unnecessarily difficult to integrate these features into trunk.

> 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