Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-6662

More concise logging

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Logging
    • Labels:
      None

      Description

      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: 20190528T11: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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                Dunemaster Vasiliy Kudriavtsev
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: