-
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
Reading standard input from plugins does not work #541
Comments
Interactions using the keyboard are currently only supported for maven plugins which use the plexus interaction layer. The For the stream decoration (i.e., the |
Fwiw, quarkus uses low level terminal interactions to set up the console support, however, there's no terminal in the daemons. At the OS level, the daemon process input stream is not used at all and the output/error streams are redirected to files. Inside the JVM, the output/error are conveyed back to the client, and the input is currently not supported. Supporting redirecting input from the client to the daemon is doable, but setting up a terminal, while in theory doable, would require additional native methods not provided by jansi at the moment (such as |
The implementation currently switches on the redirection when the daemon actually starts reading the System.in stream using InputStream.read() or InputStream.available().
The implementation currently switches on the redirection when the daemon actually starts reading the System.in stream using InputStream.read() or InputStream.available().
When using
mvnd
with a Quarkus 2.X project, the output looks different to what I'm used to withmvn
.More importantly, the keyboard input doesn't work. Is there something I need to configure?
See the two screenshots for a comparison:
mvnd (version
0.7.1-linux-amd64
):mvn:
The text was updated successfully, but these errors were encountered: