[jira] [Comment Edited] (MNG-6218) Jansi 1.13 does not recognize MinGW bash

["Hervé Boutemy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999941#comment-15999941 ] 

Hervé Boutemy edited comment on MNG-6218 at 5/7/17 4:58 PM:
------------------------------------------------------------

does it mean that JAnsi 1.16 will recognize MinGW bash or not?
notice that the good question is not even of recognizing MinGW or not: it is more "will ANSI escape codes work with MinGW bash or not"?
If MinGW bash does the ANSI escape codes rendering, the WIndows trick that JAnsi does is not useful


was (Author: hboutemy):
does it mean that JAnsi 1.16 will recognize MinGW bash or not?
I hope so

> Jansi 1.13 does not recognize MinGW bash
> ----------------------------------------
>
>                 Key: MNG-6218
>                 URL: https://issues.apache.org/jira/browse/MNG-6218
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.5.0
>         Environment: Windows Git Bash(MinGW)
>            Reporter: Daniel Heinrich
>            Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Jansi checks if the platform is Windows to decide if coloring needs to be handled differently. In the case that MinGW is detected it will handle coloring as if it was running on Unix.
> The test in Jansi 1.13 is if the enviroment variable TERM == "xterm", but MinGW returns "xterm-256color".
> Since Jansi 1.14 it checks if TERM starts with "xterm".
> see: https://github.com/fusesource/jansi/blob/jansi-project-1.14/jansi/src/main/java/org/fusesource/jansi/AnsiConsole.java#L123
> An upgrade to Jansi 1.14 or even 1.15 fixes this issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)