[
https://issues.apache.org/jira/browse/MNG-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895448#comment-16895448
]
Thorsten Glaser commented on MNG-6241:
--------------------------------------
[~michael-o] not in {{MAVEN_OPTS}}, only as explicit command line argument (and
there, {{-B}} is clearly the better choice).
Ideally, both {{-B}} and {{-Dstyle.color=never}} would have corresponding
{{settings.xml}} equivalents (and the former superset the latter), so one can
easily declare it on a Jenkins system without having to worry about individual
jobs overriding the environment variable.
> colour output cannot be disabled from settings.xml or MAVEN_OPTS
> ----------------------------------------------------------------
>
> Key: MNG-6241
> URL: https://issues.apache.org/jira/browse/MNG-6241
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: Thorsten Glaser
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> Coloured output does not look very nice in a Jenkins logfile *and* breaks
> some plugins we use, therefore I wish to disable it programmatically.
> However, looking at the source, I find it can only be disabled by passing the
> command-line options -B or -l, but not from settings.xml or via MAVEN_OPTS in
> the environment.
> I’ve worked around this by using dpkg-divert to move the mvn binary away and
> placing this…
> {{{
> # cat /usr/share/maven/bin/mvn
> #!/bin/mksh-static
> exec /usr/share/maven/bin/mvn.dpkg-dist -B "$@"
> }}}
> … in its stead, but that’s creepy at best. Please implement a setting,
> ideally for settings.xml *and* MAVEN_OPTS, to disable colour.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
