[FLUME-829] Assign unique package prefix to each module

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Done
• Affects Version/s: NG alpha 1
• Assignee: Unassigned
• Reporter: Will McQueen
• Created: 02/Nov/11 01:39
• Updated: 11/Nov/18 10:20
• Resolved: 11/Nov/18 10:20

Description

We should probably assign a unique package prefix for all source files located within each Flume NG module/project. Most projects already have such a prefix. The only two that don't are:
1) flume-ng-core project (recommend using "org.apache.flume.core" prefix)
2) flume-ng-node project (recommend using "org.apache.flume.node" prefix)

This convention of using a unique pkg prefix per module should help emphasize the logical separation of the modules.

Issue Links

• is related to: FLUME-3116 Refactor ng-core module, move sources, channels and sinks out of it