-
Notifications
You must be signed in to change notification settings - Fork 218
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
Use logger instead of System.out/System.err in JLineNativeLoader #907
Comments
Sure, can you point to the message displayed to sysout/syserr ? Or maybe raise a PR ? |
Thanks for the response. This particular error comes from I think that something like the following snippet should be fine. Could be that Warning is more adequate than Severe though.
I've already implemented an equivalent temporary hack on my side as I don't have jline as direct dependency. |
jline 3.24.1
Motivation from this request: I'm experiencing cases where jline new native libraries are forbidden to be loaded because of corporate security software installed on user machines. Basically, that software prevents execution of
dll
files ontmp
directory (in Windows user/Temp).As part of the terminal available provider detection process
JLineNativeLoader.loadNativeLibrary()
can be called one or multiple times. For each failed call messages are displayed in System.err/System.out. It seems like there is no way (except upfront disablingexec
andjni
provider) to prevent this messages polluting application startup.By using logger instead of System.out/System.err we would have the possibility to, optionally, hide those non critical errors from console.
The text was updated successfully, but these errors were encountered: