[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flume-dev
Subject:    [jira] [Updated] (FLUME-834) Rename all Flume NG artifactIDs with consistent prefix of "flume-ng"
From:       "Arvind Prabhakar (Updated) (JIRA)" <jira () apache ! org>
Date:       2012-01-31 19:14:10
Message-ID: 1754978434.12634.1328037250227.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


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

Arvind Prabhakar updated FLUME-834:
-----------------------------------

    Affects Version/s: v1.0.0
    
> 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: v1.0.0
> Reporter: Will McQueen
> 
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]