[
https://issues.apache.org/jira/browse/HBASE-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273658#comment-13273658
]
Jesse Yates commented on HBASE-5976:
------------------------------------
@Matt: why the disposition to pulling up rather than pushing down? Having not
had to do a refactor on this scale, it doesn't seem to make an appreciable
difference at first glance.
As far as hbase-cluster, sounds a lot like hbase-common: a catch-all for things
that don't quite fit.
The other thing that had shown up was having a common and a shared module (this
is bleeding into HBASE-5977 a bit here), in that one was common dependencies
and the other depends on all the other projects. I found things like the
mini-cluster tended to show up in shared. The reason I bring it up, is it might
be the right way to go for the 'first' module, which you can then pull up
things like common, server, client, etc. At this point, its just naming if we
want to go with the cluster vs. shared naming.
> 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
