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-5977) Usage of modules
Date Thu, 24 May 2012 05:48:40 GMT

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

Jesse Yates commented on HBASE-5977:

Results of hackathon today: Matt is going to start working on pulling things into an hbase-common
module for the common/utility classes. When we do a rewrite of the client (probably based
on asynchbase), then we are getting an hbase-client module. Until then, we are going to slowly
start pulling out modules as they seem necessary. 

Also, I'm going to add the hbase-common module so there is an example for how to add a new
module, but let Matt deal with the actual moving of classes (thanks matt!).
> Usage of modules 
> -----------------
>                 Key: HBASE-5977
>                 URL: https://issues.apache.org/jira/browse/HBASE-5977
>             Project: HBase
>          Issue Type: Brainstorming
>          Components: build
>    Affects Versions: 0.96.0
>            Reporter: Jesse Yates
>   Original Estimate: 336h
>  Remaining Estimate: 336h
> With HBASE-4336, HBase will have the ability to add multiple modules for different aspects
of the codebase (less tests, see HBASE-4336 for details). We need to set a policy for when
modules should be used versus putting the code into a single existing module or dispersed
across modules. 

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


View raw message