[
https://issues.apache.org/jira/browse/HBASE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270697#comment-13270697
]
Jesse Yates commented on HBASE-4336:
------------------------------------
For those looking to jump into the changes, here is basically the outline of
what is going on in hbase/pom.xml
1) moved all the dependencies into the dependencyManagement section and plugins
into pluginManagement (so submodules will all use the same version)
2) Moved the per-proflie dependencies (different versions of hadoop) into the
hbase-core pom
3) Moved all the assembly of the final package into the hbase-assemble pom
4) Different profiles are retained in the parent for setting general properties
for the children modules (e.g. test profiles for the test properties, hadoop
profiles for the hadoop versions)
5) Added a couple of dependencies/plugiuns that will probably be used by most
children (test stuff, apache-rat, etc).
6) General cleanup for spacing
> 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
> Priority: Critical
> Fix For: 0.96.0
>
>
> 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.
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
