-
Notifications
You must be signed in to change notification settings - Fork 877
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
Plugin dropping stderr output silently #142
Comments
It looks like there is some sort of race condition that causes the last line or two sent to stderr to never get printed. |
Hmm... It's s clumsy implementation of log forwarding, I'm not sure if there's a library that can do it better... |
It turns out that we're actually losing lines sent to stdout, not stderr. I tracked the down problem to nodejs/node-v0.x-archive#8329; therefore, it is not fixable. That said, I discovered a minor bug in your stderr-handling code. I will publish a PR soon. |
ProcessExecutor was logging stderr to stdout log #142
The plugin is dropping stderr output. This is 100% reproducible.
Repro steps:
gulpfile.js
containing:2.. Configure Maven as follows:
3.. Build the project.
4.. Maven fails with:
5.. Run
gulp
manually from command-line:Expected behavior: Maven should output the 3 lines shown above.
The text was updated successfully, but these errors were encountered: