[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205068#comment-16205068
]
Hudson commented on MNG-6242:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-3.x #1671 (See
[https://builds.apache.org/job/maven-3.x/1671/])
[MNG-6242] detect Cygwin/Mingw pseudo terminal for Jansi (hboutemy:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=c19e9dcac3d200094c770521b9b1b10df76f26c4])
* (edit) apache-maven/src/bin/mvn
> No color for maven on Cygwin
> ----------------------------
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> Reporter: Brian Oxley
> Assignee: Hervé Boutemy
> Priority: Minor
> Fix For: 3.5.2
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
