Skip to content
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

Show test output while running #77

Closed
blsouthr opened this issue Sep 30, 2020 · 3 comments
Closed

Show test output while running #77

blsouthr opened this issue Sep 30, 2020 · 3 comments
Milestone

Comments

@blsouthr
Copy link

Currently test output it showed after all tests are run. If one have lots of tests, its useful to see what is going on while running tests and possibly interrupt the build early if some test fails. This would save lot of time and on failures and provide the status of build while it running.

Right now, one have always wait until the end of mvnd build to see if some tests failed.

@gnodet
Copy link
Contributor

gnodet commented Sep 30, 2020

We could have such an option when running in a single threaded build. In a multithreaded build, the output is mixed between the various modules. In those cases, we could allow displaying the build log for processed modules.

Another option would be to have a small log window for each module, i.e. display the last 3 lines of the log for each module being processed below the current line for the module.

@blsouthr
Copy link
Author

That would be awesome.

gnodet added a commit to gnodet/mvnd that referenced this issue Oct 2, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 2, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 5, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 5, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 5, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 6, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 6, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 6, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
gnodet added a commit to gnodet/mvnd that referenced this issue Oct 7, 2020
All events are directly forwarded to the client.  The client is now responsible for ordering them per project and displaying them if needed.  A thread is now started to read the terminal input with support for '+' to display one more line per project, '-' to display one line less, and 'Ctrl+L' to redraw the display which could become messed if the build messages are a bit unusual (this may require a better fix though).
@gnodet gnodet closed this as completed in dd32f41 Oct 7, 2020
@ppalaga ppalaga added this to the 0.0.7 milestone Oct 19, 2020
@blsouthr
Copy link
Author

@gnodet Just installed v0.0.8 via sdkman and it still not showing the output while running the tests

Maven Daemon 0.0.8-linux-amd64 (native)
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/sdkman/candidates/mvnd/0.0.8/mvn
Java version: 14.0.1, vendor: AdoptOpenJDK, runtime: /opt/sdkman/candidates/java/14.0.1.hs-adpt
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-1031-azure", arch: "amd64", family: "unix"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants