You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Sylwester Lachiewicz (JIRA)" <ji...@apache.org> on 2019/01/13 21:40:00 UTC

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

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

Sylwester Lachiewicz closed MNG-6218.
-------------------------------------
       Resolution: Auto Closed
    Fix Version/s:     (was: waiting-for-feedback)

In Maven 3.6.0 we use JAnsi 1.17. 1 - please reopen the issue if the described problem still exists.

> 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
(v7.6.3#76005)