maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gili (JIRA)" <>
Subject [jira] [Commented] (MNG-6225) Application cannot output ANSI colors when run by Maven
Date Sat, 16 Feb 2019 20:45:00 GMT


Gili commented on MNG-6225:

[~michael-o] How would I test this? I don't see where I can download 3.6.1-SNAPSHOT binaries
for Windows.

Here is a more concise testcase for you:
 # Create a Maven project with Surefire plugin configured with <forkCount>0</forkCount>.
 # Run "mvn -Djava.library.path=X".
 # Try reading "java.library.path" from within a unit test.
 # Notice that the system property is not set.

Expected behavior: Running "mvn -D<any value>" should trigger a build failure or warning
indicating that users should use MAVEN_OPTS to set system properties.

> Application cannot output ANSI colors when run by Maven
> -------------------------------------------------------
>                 Key: MNG-6225
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line, core
>    Affects Versions: 3.5.0
>            Reporter: Gili
>            Priority: Major
> I'm not sure which Maven component this bug report belongs to (please reassign if needed).
> This is a follow-up to
> To recap: someone (probably Maven core) is redirecting the native stdout handle when
running plugins such as Surefire. This prevents applications from outputting ANSI colors under
Windows 10 because:
> * Applications must explicitly enable ANSI support using JNI.
> * The JNI calls fail if the stdout handle has been redirected.
> If I run the exact same application outside of Maven, JNI no longer detects that stdout
has been redirected and ANSI colors as expected.
> Any idea who is doing the redirection, and how to disable it?

This message was sent by Atlassian JIRA

View raw message