[ https://issues.apache.org/jira/browse/MNG-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385375#comment-17385375 ]
Henning Hoefer commented on MNG-6380: ------------------------------------- I tried it in `maven-3.8.x` [3.8.2-SNAPSHOT (c395ca976dc9eaed65dcdc0037508d1edbfb57f3)] and in `master` [4.0.0-alpha-1-SNAPSHOT (0696cf14adec8fc4939b938844cfa93f421c1dfe)] and it worked in both. :) > 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 > Fix For: waiting-for-feedback > > > 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)