You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Oxley (JIRA)" <ji...@apache.org> on 2017/09/17 01:38:00 UTC

[jira] [Commented] (MNG-6242) No color for maven on Cygwin

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

Brian Oxley commented on MNG-6242:
----------------------------------

Please note, this work around seems effective, at least for me:

https://plus.google.com/111012722058314768782/posts/Z8ufa5LS6nv

Perhaps while waiting on JAnsi change for Cygwin, the mvn script could be updated to include adding `-Djansi.passthrough=true` to MAVEN_OPTS?


> 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
>            Priority: Minor
>
> 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)