[HBASE-4336] Convert source tree into maven modules

• Type: Task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.95.0
• Component/s: build
• Assignee: Jesse Yates
• Reporter: Gary Helmling
• Created: 06/Sep/11 22:39
• Updated: 23/Sep/13 18:30
• Resolved: 04/Jun/12 21:23

Description

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.

Issue Links

• blocks: HBASE-6087 Add hbase-common module
• depends upon: HBASE-5976 Initial module naming
• is depended upon by: HBASE-5977 Usage of modules
• is related to: GIRAPH-346 Top Level POM
• is related to: HBASE-4438 Speed the build test phase
• is related to: HBASE-4602 Make the suite run in at least half the time
• relates to: HBASE-4676 Prefix Compression - Trie data block encoding
• relates to: HBASE-5341 Push the security 0.92 profile to maven repo