Allow for a sorted log when --batch-mode is used in a multi module project

[royscheefhals]

Hello!

We use maven-daemon to allow for a much better developer experience when dealing with multi module projects.
We also use parallel builds in our CI/CD pipelines, but this is currently using regular maven mvn -T <threads> .

Using parallel builds with regular maven results in an unsorted build logfile, rendering it almost unusable.

We're looking at using maven daemon to allow for a sorted log, but unfortunately using mvnd clean --batch-mode also results in an unsorted logfile. Although, it does prepend each logline tags in the form of [project_id] <message>.

I located the line that eventually directly prints the tagged logline:

maven-mvnd/common/src/main/java/org/mvndaemon/mvnd/common/logging/TerminalOutput.java

Lines 392 to 404 in 9f4b57b

	if (prj == null) {
	log.accept(bm.getMessage());
	} else if (noBuffering || dumb) {
	String msg;
	if (maxThreads > 1) {
	msg = String.format("[%s] %s", bm.getProjectId(), bm.getMessage());
	} else {
	msg = bm.getMessage();
	}
	log.accept(msg);
	} else {
	prj.log.add(bm.getMessage());
	}

Line 401 is what is printed

My Suggestion

Why not remove the block L394-L401 and just allow for the log to still be buffered per project?

So, just always do prj.log.add(bm.getMessage());.

What are your thoughts?