Fix #11885: Disable ANSI colors when stdout is piped on JDK 22+#11887
Draft
Fix #11885: Disable ANSI colors when stdout is piped on JDK 22+#11887
Conversation
… JDK 22+ Change ForcedSysOut to SysOut so that JLine properly checks whether stdout is a TTY before creating a system terminal. ForcedSysOut bypasses this check, which causes JLine to create a non-dumb terminal even when stdout is piped (since stdin is still a TTY), resulting in ANSI escape codes appearing in piped output on JDK 22+ where the FFM provider successfully creates a terminal from stdin alone. With SysOut, JLine detects that stdout is not a TTY and falls back to a dumb terminal, correctly disabling ANSI colors. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
slawekjaranowski
approved these changes
Apr 7, 2026
Member
slawekjaranowski
left a comment
slawekjaranowski
left a comment
There was a problem hiding this comment.
Test plan pass locally
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ForcedSysOuttoSysOutin JLine'sTerminalBuilderconfiguration so that JLine properly checks whether stdout is a TTY before creating a system terminalForcedSysOutbypasses TTY detection, causing a non-dumb terminal to be created even when stdout is piped (because stdin is still a TTY), resulting in ANSI escape codes in piped output on JDK 22+ where the FFM provider creates a terminal from stdin aloneRoot Cause
JLine's
SystemOutput.ForcedSysOutalways returnsSystemStream.Outputinselect()without checking if stdout is actually a TTY. On JDK 21, the exec/JNI providers would fail to create a system terminal when stdout was piped, falling back to dumb. On JDK 22+ with the FFM provider, the terminal is created successfully (stdin is a TTY), producing a non-dumb terminal with colors enabled even when piped.SystemOutput.SysOutdoes the right thing: it checks if stdout is a TTY first. If not,systemStreamis null, and JLine falls back to a dumb terminal — exactly the correct behavior.Test plan
mvn help:help -X | lessshould show plain text (no ANSI codes) on JDK 25+mvn help:help -X > /tmp/out.txtshould produce plain text on JDK 25+mvn help:help -Xshould still show colored output on a real terminalmvn --color=always help:help -X | lessshould still show ANSI codes (forced)mvn --color=never help:help -Xshould show plain textFixes #11885
Claude Code on behalf of Guillaume Nodet
🤖 Generated with Claude Code