You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like the terminal logger feature but it has a big pitfall, it breaks all the outputs by default which means any failing build needs to run without it more or less.
What would be neat is to keep the terminal logger feature AND the output.
One way is to "split" the output in two parts, the build output (at the top for ex) and the "dynamic" output (tl) at the bottom - think gradle does it or was doing it at least.
An alternative is what maven daemon does (once well configured), ie assign N lines (N >= 1) per project, have the first line being the terminal logger and the other lines the build output of this project. Finally you stack the projects and you get an in between feedback.
Last option is to just dump the output on failure (capturing in a file during the build for ex).
Hope it makes sense
The text was updated successfully, but these errors were encountered:
Hi,
I really like the terminal logger feature but it has a big pitfall, it breaks all the outputs by default which means any failing build needs to run without it more or less.
What would be neat is to keep the terminal logger feature AND the output.
One way is to "split" the output in two parts, the build output (at the top for ex) and the "dynamic" output (tl) at the bottom - think gradle does it or was doing it at least.
An alternative is what maven daemon does (once well configured), ie assign N lines (N >= 1) per project, have the first line being the terminal logger and the other lines the build output of this project. Finally you stack the projects and you get an in between feedback.
Last option is to just dump the output on failure (capturing in a file during the build for ex).
Hope it makes sense
The text was updated successfully, but these errors were encountered: