[ https://issues.apache.org/jira/browse/HBASE-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271943#comment-13271943 ]
Lars Hofhansl commented on HBASE-5976: -------------------------------------- hbase-common makes the most sense to me. After a while we'll split out some client and some server classes. @Matt: On the mailing list you mentioned you wanted to pull out some "core" classes like KeyValue, etc. Where would these go? > Initial module naming > --------------------- > > Key: HBASE-5976 > URL: https://issues.apache.org/jira/browse/HBASE-5976 > Project: HBase > Issue Type: Brainstorming > Components: build > Affects Versions: 0.96.0 > Reporter: Jesse Yates > Original Estimate: 336h > Remaining Estimate: 336h > > There is currently a lot of discussion around the 'right' name for the > initial module that will host all the code in the primary modularization of > hbase. The current contenders are: > * hbase-core > * hbase-common > * hbase-server > * hbase-bucket > * hbase-hbase > Let's duke it out and pick the best, while keeping in mind that this module > will *not* remain the sole module going forward, but is merely the precursor > Timeline to close this issue is the day before the code gets committed. > Source: > http://search-hadoop.com/m/pwi1t1e9K0R/modularizing+trunk&subj=modularizing+trunk -- 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