maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MNG-6218) Jansi 1.13 does not recognize MinGW bash
Date Thu, 11 May 2017 06:18:04 GMT

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

Hervé Boutemy commented on MNG-6218:
------------------------------------

[~DannyNullZwo], I just proposed a pull request to make jansi.jar executable to easily test
it in any conditions, without requiring integration in Maven or any other end-user tool: see
https://github.com/fusesource/jansi/pull/88
For now, you'll need to import the PR and build the lib for yourself to test it in any conditions
and report the results

> 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)

Mime
View raw message