[
https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973023#comment-15973023
]
ASF GitHub Bot commented on MNG-6220:
-------------------------------------
Github user mryan43 commented on the issue:
https://github.com/apache/maven/pull/114
Unfortunately, the system property is read only once in a static init block
in the JansiConsole class before the cli main method is invoked, so my change
doesn't work.
We have a kind of chicken and egg situation and we need to decide if we
prefer
a) not setting up Jansi until arguments/config have been parsed and
validated (and call MessageUtils.systemInstall(); later in the loggin() method)
b) forcing jansi until arguments and config have been parsed (by adding
System.setProperty( "jansi.force", "true" ); before
MessageUtils.systemInstall(); in MavenCli#main and then eventually disable it
later in the loggin() method
What do you think ?
> 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)
