[
https://issues.apache.org/jira/browse/MNG-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242093#comment-17242093
]
Guillaume Nodet commented on MNG-6380:
--------------------------------------
[~michael-o] here's one possibility
https://github.com/apache/maven-shared-utils/pull/67
Another one would be to defer the call to `AnsiConsole.systemInstall()` a bit
to do it in `MavenCli.logging()` in a similar way, but just do a
`AnsiConsole.systemInstall()` instead of a `AnsiConsole.systemReinstall()`
> Option -Dstyle.color=always doesn't force color output
> ------------------------------------------------------
>
> Key: MNG-6380
> URL: https://issues.apache.org/jira/browse/MNG-6380
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.5.3
> Reporter: Henning Hoefer
> Priority: Minor
> Labels: workaround-exists
>
> When the output is not a TTY (e.g. on a CI server), the new option
> {{-Dstyle.color=always}} doesn't work, because JAnsi itself is disabling its
> color output.
> {code:bash}
> # OK, produces color:
> mvn -B -Dstyle.color=always package
> # FAIL, doesn't produce color:
> mvn -B -Dstyle.color=always package | less -R
> # WORKAROUND:
> MAVEN_OPTS=-Djansi.force=true mvn -B -Dstyle.color=always package | less -R
> {code}
> The {{-Dstyle.color=always}} option needs to imply {{-Djansi.force=true}} –
> otherwise, "always" doesn't really mean always.
> The problem for the implementation is, that the JAnsi option needs to be set
> as a system property way early during startup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
