-
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
Option to default to a simple log when using a single thread #116
Comments
Hitting the |
Confirmed, thanks!
Well, if I would see the condensed status as described in README (which I don't, maybe because of #36?), then I would actually prefer the less noisy mode to be the default. Btw, is there something like |
I would really like to opt out of the custom display (which by the way is broken in Emacs’ |
Could you please file a separate issue?
Could you please file a separate issue in which you explain why? |
Another reason to want output to be displayed normally as it arrives: watching the progress of tests. I actually rolled back a Surefire update just because it broke this: jenkinsci/plugin-pom#343 |
@jglick the progress can also be seen in more details if you hit the '+' key 3/4 times during the build... (hit '-' to get revert). |
I wonder, if we could automatically stretch the rolling log to the full screen in case there is just a single thread running? |
@ppalaga I was thinking about:
Maybe the first two can be the same. It's just that we add the prefix if the build has a max number of threads > 1. |
It would come in handy to able to opt-out of the log buffering in case you want a more default maven output, e.g. to compare runs to
mvn
in casemvnd
is showing unexpected behaviour.When building Quarkus with its 700+ modules, console can also become unresponsive for a while when everything is flushed at once at the end of the build.
The text was updated successfully, but these errors were encountered: