[
https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972657#comment-15972657
]
ASF GitHub Bot commented on MNG-6220:
-------------------------------------
Github user michael-o commented on the issue:
https://github.com/apache/maven/pull/114
They are several issues. People are used to
[GNU](https://www.gnu.org/software/grep/manual/grep.html#General-Output-Control)
and [BSD](https://www.freebsd.org/cgi/man.cgi?query=grep&sourceid=opensearch)
tools like grep. They use values `never`, `always`, `auto`. Having said that I
do think we need to do this exactly the same way:
[`grep.c`](https://github.com/freebsd/freebsd/blob/master/usr.bin/grep/grep.c#L627-L647).
Option `always` requires special attention due to `isatty` in combination with
`less(1)`.
> 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
>
> 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.3.15#6346)
