-
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
Support launching processes with inherited IO #241
Milestone
Comments
Yes, this is caused by the quarkus maven plugin spawning a process. It does use the |
I see 2 solutions:
|
The first solution can't be done easily, so a change to quarkus maven plugin is the best solution imho. |
gnodet
added a commit
to gnodet/mvnd
that referenced
this issue
Jan 5, 2021
gnodet
added a commit
to gnodet/mvnd
that referenced
this issue
Jan 5, 2021
gnodet
changed the title
Support launching processes with inherited IO
Jan 5, 2021
-Dmvnd.noBuffering=true
doesn't show quarkus:dev output
gnodet
added a commit
to gnodet/mvnd
that referenced
this issue
Jan 5, 2021
gnodet
added a commit
to gnodet/mvnd
that referenced
this issue
Jan 5, 2021
gnodet
added a commit
to gnodet/mvnd
that referenced
this issue
Jan 6, 2021
gnodet
added a commit
to gnodet/mvnd
that referenced
this issue
Jan 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create and unzip the simplest quarkus app possible. When running
mvn quarkus:dev
, the server logs are displayed following the maven traces:Now, using mvnd 0.1.1, with
mvnd quarkus:dev -Dmvnd.noBuffering=true
, the application logs are not shown (which is an issue for vscode-quarkus, since it can't detect the debugger is available):at that point, the server is actually running, but there's no clue from the output.
I suspect this will be a similar issue with other microservices or processes spawned from maven plugins
The text was updated successfully, but these errors were encountered: