[ 
https://issues.apache.org/jira/browse/MNG-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Heinrich updated MNG-6218:
---------------------------------
    Description: 
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.3 is if the enviroment variable TERM == "xterm", but MinGW 
returns "xterm-256color".
Since Jansi 1.4 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.4 or even 1.5 fixes this issue.

  was:
Jansi use 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 some Unix.

The test in Jansi 1.3 is if the enviroment variable TERM == "xterm", but MinGW 
returns "xterm-256color".
Since Jansi 1.4 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.4 or even 1.5 fixes this issue.


> Jansi 1.3 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.3 is if the enviroment variable TERM == "xterm", but 
> MinGW returns "xterm-256color".
> Since Jansi 1.4 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.4 or even 1.5 fixes this issue.



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

Reply via email to