[
https://issues.apache.org/jira/browse/HBASE-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271867#comment-13271867
]
Jesse Yates commented on HBASE-5976:
------------------------------------
I went with hbase-core in the original naming because that is where the core of
all the code is going to be placed. However, this has come up over and over to
be confusing.
+1 on hbase-common. This is a package we are going to need anyways going
forward, so we might as well name it that.
Having throw away names like hbase-bucket or hbase-hbase are tricky because
there is a chance we get stuck with the names or have a release where they are
named that way and end up with a mess like we have currently in different
hadoop versions and the artifact naming they use (which is all over the map and
nearly completely independent between versions). Also, I'd rather save work in
doing another rename.
Finally, against hbase-server for the reason in the email thread that
{quote}
If we started with hbase-server there would be a while until all of the client
and other
packages were split up where org.apache.hadoop.hbase.client was in the
hadoop-server jar.
- Elliot Clark
{quote}
Further, we don't have a timeline for when the other modules are going to be
pulled out, so we could be stuck in this weird naming scheme for a while.
> 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
