If Maven Daemon executes in 0.2s, the summary output might be printed too early

[bmarwell]

Hi,

at a demo at JCON, our build ran in 0.2s (using the cache extension).
The Summary output at the end was not the last to be printed; mvnd was not done printing other entries from the buffer yet, so I had to scroll up for the project summary.

This does usually not happen, because usually it takes 0.6 seconds to complete.
So, there is a timing issue.

Maven Daemon should wait at least until the buffer has been emptied to the console.

Will try to grab a screenshot.

[bmarwell]

I could not reproduce it anymore, even though it ran in 1.8s.