slachiewicz commented on issue #14080:
URL: https://github.com/apache/maven/issues/14080#issuecomment-7064725004

   Thanks for the detailed report and analysis — you diagnosed it correctly.
   
   `WriterOutputStream` in JLine 3.30.17 is not thread-safe: it keeps a shared 
`ByteBuffer`/`CharBuffer` for decoding and mutates them in 
`write()`/`processInput()` without synchronization. Maven 3.10.0 installed 
JLine's `AnsiConsole` streams, so `System.out` and `System.err` both ended up 
writing into the same `WriterOutputStream`; under `-T8` concurrent logging 
corrupted its buffer position and the `IllegalArgumentException` escaped the 
logging call into the mojo that happened to be logging. That is why it was 
intermittent and why a logging failure broke the build.
   
   This path was removed in Maven 3.10.1: we no longer install JLine's console 
streams or replace `System.out`/`System.err` (see apache/maven#13888 / commit 
`6530a35fd9`). Maven now only emits ANSI escape codes itself, so 
`WriterOutputStream` is no longer on Maven's logging path. Closing this as 
fixed in 3.10.1 — please reopen if you can still reproduce it there.
   
   We are following up upstream as well, since the underlying 
`WriterOutputStream` thread-safety issue is in JLine and affects both 3.x and 
4.x: https://github.com/jline/jline3/issues/2455.
   


-- 
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]

Reply via email to