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 ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
