[jira] [Resolved] (FLUME-834) Rename all Flume NG artifactIDs with consistent prefix of "flume-ng"

["Ferenc Szabo (JIRA)" <ji...@apache.org>]

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

Ferenc Szabo resolved FLUME-834.
--------------------------------
    Resolution: Fixed

> Rename all Flume NG artifactIDs with consistent prefix of "flume-ng"
> --------------------------------------------------------------------
>
>                 Key: FLUME-834
>                 URL: https://issues.apache.org/jira/browse/FLUME-834
>             Project: Flume
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 1.0.0
>            Reporter: Will McQueen
>            Priority: Major
>
> We should by convention name all of our Flume NG artifacts with the same "flume-ng" prefix. This requires changing the <artifactId> in the pom files. Our current artifactIDs are:
> (1) flume-file-channel (change to flume-ng-file-channel)
> (2) flume-jdbc-channel (change to flume-ng-jdbc-channel)
> (3) flume-hdfs-sink (change to flume-ng-hdfs-sink)
> (4) flume-ng-core
> (5) flume-ng-node
> (6) flume-ng-dist
> As a result of this convention, the corresponding eclipse project names would all start with "flume-ng" and be easily distinguishable from Flume OG projects, when both are kept in the same workspace.



--
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