You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flume.apache.org by "Ferenc Szabo (JIRA)" <ji...@apache.org> on 2018/11/11 10:21:00 UTC

[jira] [Resolved] (FLUME-829) Assign unique package prefix to each module

     [ https://issues.apache.org/jira/browse/FLUME-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ferenc Szabo resolved FLUME-829.
--------------------------------
    Resolution: Done

> Assign unique package prefix to each module
> -------------------------------------------
>
>                 Key: FLUME-829
>                 URL: https://issues.apache.org/jira/browse/FLUME-829
>             Project: Flume
>          Issue Type: Improvement
>    Affects Versions: NG alpha 1
>            Reporter: Will McQueen
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org