[
https://issues.apache.org/jira/browse/MNG-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161977#comment-16161977
]
Hervé Boutemy commented on MNG-6282:
------------------------------------
this is probably the offending commit...
and if we downgrade in Maven Jansi from 1.16 to 1.15, this will revert MNG-6205
since https://github.com/fusesource/jansi/pull/79 won't be merged
[~dejan2609] can you try with {{-Djansi.force=true}}? this is a property I
found while working on https://github.com/fusesource/jansi/pull/88
Then, on the conditions to reproduce the detection bug in JAnsi, I think we'll
really need to define precisely the different shells: is Git Bash different
from Cygwin?
Or in fact, it's more JAnsi project that will require this, because from
version to version, one fix for one shell cause a regression on another shell.
Was an issue opened in JAnsi?
(remember: https://github.com/fusesource/jansi/pull/88 will ease standalone
JAnsi tests, without waiting Maven to be victim of such a regression in
JAnsi...)
> Console output has no colors (regression in Maven 3.5.1)
> --------------------------------------------------------
>
> Key: MNG-6282
> URL: https://issues.apache.org/jira/browse/MNG-6282
> Project: Maven
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.5.1
> Reporter: Dejan Stojadinović
> Labels: regression, windows
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.png
>
>
> See
> [screenshot|https://issues.apache.org/jira/secure/attachment/12886398/screenshot-1.png]
> for more details.
> _*Environment:*_
> * Windows 10, 64 bit
> * Oracle Java, version: *1.8.0_144*
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
