Pankraz76 opened a new pull request, #13747: URL: https://github.com/apache/maven/pull/13747
When stdout is piped or redirected, JLine falls back to a dumb system terminal writing to an unbuffered FileOutputStream behind a FilterOutputStream, and AnsiOutputStream only implements write(int), so every byte became its own write(2) system call. Replace that terminal with an equivalent DumbTerminal writing to the same file descriptor through an 8 KiB synchronized buffer, as Jansi 2.x did in Maven 3.9.x. The auto-flushing AnsiPrintStream still flushes per line and on explicit flush, and uninstalling flushes what is left. Claude-Session: https://claude.ai/code/session_01MTr23wrhAGcyk6rY5W3XKU <!-- Please open pull requests against one of the following branches: - master — default target for all changes (new features + bug fixes). If the change should also go to maven-4.0.x, request a backport in the PR. - maven-3.10.x — target for 3.x changes (new features + bug fixes). If the change should also go to maven-3.9.x, request a backport in the PR. maven-3.9.x should receive only serious bug fixes, as it is approaching EOL. Backports are typically handled by maintainers; however, after agreement you may open a separate backport PR to the target maintenance branch. --> <!-- Add your description here... what, why and how you resolve the issue --> --- To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) check one of the following: - [ ] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) - [ ] I hereby declare that I have filed an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
