[
https://issues.apache.org/jira/browse/MNG-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849595#comment-16849595
]
Michael Osipov commented on MNG-6662:
-------------------------------------
Maybe we should work with SLF4J markers which are passed to Logback to be
filtered?
> More concise logging
> --------------------
>
> Key: MNG-6662
> URL: https://issues.apache.org/jira/browse/MNG-6662
> Project: Maven
> Issue Type: Improvement
> Components: Logging
> Reporter: Vasiliy Kudriavtsev
> Priority: Minor
>
> Maven supports configurable logging, but sometimes even more flexibility is
> required.
> ExecutionEventLogger logs build events, but in a big (280+) modules its
> output is redundant, and slows down execution as it is logged to console. (+5
> sec to a 60 sec build, 6-core Core i7, 32 GB RAM, -T8 parallelism)
> I dont need in log a lot of information like this:
>
> {{INFO}}{{] — maven-clean-plugin:}}{{3}}{{.}}{{0}}{{.}}{{0}}{{:clean}}
> {{(default-clean) @ executor ---}}
> {{[}}\{{INFO}}{{]}}
> {{[}}\{{INFO}}{{] —
> flatten-maven-plugin:}}{{1}}{{.}}{{1}}{{.}}{{0}}{{:clean}} {{(flatten.clean)
> @ executor ---}}
> {{[}}\{{INFO}}{{]}}
> {{[}}\{{INFO}}{{] —
> build-helper-maven-plugin:}}{{1}}{{.}}{{9}}{{.}}{{1}}{{:parse}}{{-version
> (parse-version) @ executor ---}}
> {{[}}\{{INFO}}{{]}}
> {{[}}\{{INFO}}{{] —
> maven-enforcer-plugin:}}{{3}}{{.}}{{0}}{{.}}{{0}}{{-}}{{M1}}{{:enforce}}
> {{(enforce-tools) @ executor ---}}
> {{[}}\{{INFO}}{{]}}
> {{[}}\{{INFO}}{{] — buildnumber-maven-plugin:}}{{1}}{{.3_p1}}{{:create}}
> {{(build-commit) @ executor ---}}
>
> Still, I would like to see build summary in the end, like
> {{Reactor Summary }}{{for}} {{g5-xbsl-executor
> }}{{0}}{{.}}{{0}}{{.}}{{57}}{{-}}{{72}}{{:}}
> {{[}}\{{INFO}}{{]}}
> {{[}}\{{INFO}}{{] g5-xbsl-executor ...................................
> }}{{SUCCESS}} {{[ }}\{{0}}\{{.}}\{{963}} {{s]}}
> {{[}}\{{INFO}}{{] com.e1c.g5.executor.compiletime ....................
> }}{{SUCCESS}} {{[ }}\{{3}}\{{.}}\{{485}} {{s]}}
> {{[}}\{{INFO}}{{] com.e1c.g5.executor.runtime ........................
> }}{{SUCCESS}} {{[ }}\{{7}}\{{.}}\{{171}} {{s]}}
> {{[}}\{{INFO}}{{] com.e1c.g5.executor.core ...........................
> }}{{SUCCESS}} {{[ }}\{{2}}\{{.}}\{{762}} {{s]}}
> {{[}}\{{INFO}}{{] com.e1c.g5.executor.client .........................
> }}{{SUCCESS}} {{[ }}\{{12}}\{{.}}\{{966}} {{s]}}
> {{[}}\{{INFO}}{{] com.e1c.g5.executor.idesupport .....................
> }}{{SUCCESS}} {{[ }}\{{6}}\{{.}}\{{848}} {{s]}}
> {{[}}\{{INFO}}{{]
> ------------------------------------------------------------------------}}
> {{[}}\{{INFO}}{{] }}{{BUILD}} {{SUCCESS}}
> {{[}}\{{INFO}}{{]
> ------------------------------------------------------------------------}}
> {{[}}\{{INFO}}{{] Total time: }}{{32}}{{.}}{{135}} {{s (Wall Clock)}}
> {{[}}\{{INFO}}{{] Finished at:
> }}{{2019}}{-}{{05}}{-}{{28T11}}{{:}}{{57}}{{:}}{{40}}{{+}}{{03}}{{:}}{{00}}
>
>
> I propose adding a new command-line option, for example -cbl
> (-concise-build-logging) to force ExecutionEventLogger log only
> projectDiscoveryStarted
> sessionStarted
> sessionEnded
> projectStarted
> projectSkipped
> thus excluding mojo-related events
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
