[
https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974178#comment-15974178
]
Manuel Ryan commented on MNG-6220:
----------------------------------
Hello [~rfscholte] and [~aheritier]
A system property or environment variable would be ok for CI use cases, but a
programmatic extension point for this is a bit more cumbersome as it would need
specific integration code in all CI systems when they already support cli
options and env vars out of the box.
We also need to consider how existing CLI options influence color (-B and -l).
Configuring color behavior elsewhere could make it a harder to understand what
is happening as some cli options would be starting to override system
properties or vice-versa.
> 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)
