-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No color/ansi support on Windows with 1.0.0? #1032
Comments
I downloaded Windows mvnd 1.0.0 distro, opened it up, and the file is there... so unsure what happens. |
Ah sorry, that was a copy & paste error, I added The fix for the native client probably needs to be something different?!? |
Yes, #1033 is exactly about that (adding missing native) plus adding "diag" cmd |
Fixing terminal on Windows. changes: * added missing jline-native to dist * up GraalVM to 22 * introduce `--diag` on client * up SVM version, cleanup of GraalVM params Fixes #1032
Fixed with #1040 |
Please retest with binaries built by CI from here: |
@cstamas Works! Thanks! |
When using mvnd 1.0 on Windows, I get this error:
Digging deeper² the problem seems to be that no native access provider is packaged with jansi/jline:
Debugging output
And indeed, putting (for example)
jline-terminal-jni-3.26.1.jar
intomaven-mvnd-1.0.0-windows-amd64/mvn/lib/mvnd
fixes the error.Details for reproduction
² To get to this debug output I had to use the JVM wrapper (
set MVND_CLIENT=jvm
) and create a logging configuration like this:and instruct the wrapper to use it:
The text was updated successfully, but these errors were encountered: