Karm Michal Babacek

@geoand Oh, I see.

Workaround is to remove dependency on `quarkus-junit5` and tests as that brings in the readline/jansi... Merely disabling tests like so is not enough: ``` C:\tmp\code-with-quarkus λ mvnw clean package -Dnative...

Update, the actual culprit is jboss-logmanager and what it does internally that allows e.g. color print via JDK's internal jline terminal control devices. It needs additional config ``` ... {...

This reproduces the issue in isolation, without Quarkus in the picture: https://github.com/Karm/dev-null/tree/main/jbosslogmanager Linux: OK Windows exactly the same error as Quarkus: ``` C:\tmp\dev-null\jbosslogmanager(main -> origin) λ native-image --no-fallback --link-at-build-time --initialize-at-build-time=org.jboss,io.smallrye...

The trace with a different terminal, plain cmd, looks diferently. It's not about color after all. In this case, jbosslogmanager bails out and * doesn't attempt to insert any color...

I have narrowed it down to the switch between jline *internal* to JDK being opt-in up to JDK 21 and default later, e.g. in JDK 23+ where I am reproducing...

Updated with workaround: ``` mvnw package -Dnative -Dquarkus.native.additional-build-args=-J-Djdk.console=jdk.base ```

@sergeevabc if you call native-image manually, outside Quarkus build process, you just append `-J-Djdk.console=jdk.base`. This issue has nothing to do with Quarkus per se. `quarkus.native.additional-build-args` is just Quarkus' way of...

So, the default console is back to what it was, `jdk.console=jdk.base` and this workaround is apparently not needed any more beginning JDK 25. I'll double check on more Windows terminals...

Closing. Not an issue with 25 LTS.