[ACCUMULO-658] refactor code into separate modules where appropriate

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Assignee: Christopher Tubbs
• Reporter: Adam Fuchs
• Created: 27/Jun/12 18:13
• Updated: 02/Apr/14 14:54
• Resolved: 01/Nov/13 00:56

Description

This ticket is a parent of several other tickets, under which we can discuss the merits of separating or grouping particular modules into more or fewer maven projects. Here's a list of pros and cons:

Pros:

• Explicit modularity encourages reuse outside of Accumulo.
• Smaller projects encourage participation in coding project-local features.
• Projects like the shell and the monitor can be exemplars for new projects or applications built on top of Accumulo.
• Separating projects forces use of publicly accessible APIs instead of custom connections. This is a form of dogfooding, and helps code quality.

Cons:

• More projects means more maven configuration, particularly in downstream projects that are dependent on multiple projects.
• Coding features across projects might be harder to comprehend and to test.
• In the extreme case, we may see public API bloat in order to support too diverse a set of projects.

Discuss...

Issue Links

• breaks: ACCUMULO-1843 NativeMap Makefile creates incorrect output file for OSX
• contains: ACCUMULO-656 move monitor code out of server
• contains: ACCUMULO-655 move test code from server package into its own package
• contains: ACCUMULO-647 Make FATE a separate module
• is depended upon by: ACCUMULO-210 create packages that enable accumulo features on the given node
• relates to: ACCUMULO-1860 NativeMapIT fails
• relates to: ACCUMULO-1885 README shows steps to build native libraries which are not valid anymore

Sub-Tasks

• move monitor code out of server: Resolved