From notifications-return-2697-archive-asf-public=cust-asf.ponee.io@fluo.apache.org Tue Feb 20 19:35:57 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 62E6E180654 for ; Tue, 20 Feb 2018 19:35:57 +0100 (CET) Received: (qmail 5326 invoked by uid 500); 20 Feb 2018 18:35:56 -0000 Mailing-List: contact notifications-help@fluo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.apache.org Delivered-To: mailing list notifications@fluo.apache.org Received: (qmail 5317 invoked by uid 99); 20 Feb 2018 18:35:56 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Feb 2018 18:35:56 +0000 From: GitBox To: notifications@fluo.apache.org Subject: [GitHub] alanblueshift commented on issue #984: Create option for machine readable output for scan Message-ID: <151915175591.21161.11328598412964755181.gitbox@gitbox.apache.org> alanblueshift commented on issue #984: Create option for machine readable output for scan URL: https://github.com/apache/fluo/issues/984#issuecomment-367074899 About the config in the command line, I believe is possible keep both. It?s a good idea! The command line could overwrite the property config. Even if the user don?t inform any parameter on command line or on property file we going to assume the **DEFAUL** behavior of the component (commons csv). About the short names. Sounds good! Done! About the dependence, is it common this two versions of the same component? How can I test properly if the upgrade works well? Any idea? Detail: with the version 2.2.4 it was not possible to write the json file. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services