[MNG-7008] skip reactor logging

[jira-importer]

Delany opened MNG-7008 and commented

Can we have a way to skip reactor logging, i.e. the reactor build order and/or reactor summary.

I have hundreds of modules in my reactor build and I always have to scroll back pages to see the error message.

---

Affects: 3.6.3

[jira-importer]

Michael Osipov commented

What about using warm level only?

[jira-importer]

Delany commented

Thanks that helps to use

  -Dorg.slf4j.simpleLogger.defaultLogLevel=warn

I see mvn -w isn't taken yet. Maybe this could join -q -e and -X?

 

However, if there are no warnings, I don't see the progress of my build.

[jira-importer]

Michael Osipov commented

I not fully convinced wether we should expose even more switches for SLF4J Simple. I t might geht even more confusing. Does the warn level help? FTR, quiet sets logger to error level which is fine im ho.

[jira-importer]

Delany commented

mvn install -T1 -Dorg.slf4j.simpleLogger.showThreadName=true | grep -v --color=always '\[main\]' | sed 's:[^]]*] ::'

[slawekjaranowski]

a proposition for fix:

• In failed build limit reactor summary to only failed modules #11977

[rmannibucau]

#13136 tries to make this report useful without breaking the human facing information of the report so idea is to replace "skip reactor logging" by "sort reactor logging by status" (failures at the end)

[gnodet]

Note: the "show only failed modules in reactor summary" behaviour introduced by #11977 (3.10.x) and #12330 (master/4.0.x) has been reverted by #13136 (merged to master) and its backport #13167 (targeting maven-4.0.x), as it caused a regression reported in #13135 — the summary looked like only one module had been built at all, which was confusing.

The approach taken in #13136 is different: show all modules but sort them by status (SKIPPED first, SUCCESS next, FAILURE last), so failures always appear at the bottom where the terminal cursor sits. This keeps the summary complete while still making failures easy to spot.

The "show only failed modules" behaviour is therefore no longer active on Maven 4.x as of 4.0.0-rc-7 / 4.1.0.