Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 25F0E200D33 for ; Wed, 8 Nov 2017 17:45:23 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 22947160BDA; Wed, 8 Nov 2017 16:45:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 692181609E0 for ; Wed, 8 Nov 2017 17:45:22 +0100 (CET) Received: (qmail 49472 invoked by uid 500); 8 Nov 2017 16:45:21 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 49461 invoked by uid 99); 8 Nov 2017 16:45:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2017 16:45:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 282AA1A2374 for ; Wed, 8 Nov 2017 16:45:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id FdZ51330MbwN for ; Wed, 8 Nov 2017 16:45:20 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F361B61232 for ; Wed, 8 Nov 2017 16:36:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 90361E2579 for ; Wed, 8 Nov 2017 16:36:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E0B7D241B3 for ; Wed, 8 Nov 2017 16:36:00 +0000 (UTC) Date: Wed, 8 Nov 2017 16:36:00 +0000 (UTC) From: "Jesse Glick (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MNG-6220) Add CLI options to control color output MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 08 Nov 2017 16:45:23 -0000 [ https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244271#comment-16244271 ] Jesse Glick commented on MNG-6220: ---------------------------------- I was directed to MNG-6296 which tracks the problem. > Add CLI options to control color output > --------------------------------------- > > Key: MNG-6220 > URL: https://issues.apache.org/jira/browse/MNG-6220 > Project: Maven > Issue Type: New Feature > Reporter: Manuel Ryan > Assignee: Robert Scholte > Fix For: 3.5.2 > > > Currently, the only way to enable/disable color output is to use the batch-mode or log-file options. > If a user wants colored output but no interactivity (ie: jenkins environment with the ansicolor plugin), there is no CLI option combination to support the use-case. > I propose to add an option to control output coloring directly. > {noformat} > --color=enabled <- color output always enabled > --color=disabled <- color output always disabled > --color=auto <- current behavior (default) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)