Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-19396

Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger

    • 3.24

      After upgrading from 1.525 to 1.528 there is a lot of extra logging in our Maven build logs. This makes it hard to read the logs. It still happens in 1.529

      It is the org.apache.maven.cli.event.ExecutionEventLogger entries.

      Note:
      They are multimodule maven builds
      Timestamper plugin is active so Time is duplicated in the logs below:

      16:47:28 Aug 27, 2013 4:47:29 PM org.apache.maven.cli.event.ExecutionEventLogger projectDiscoveryStarted
      16:47:28 INFO: Scanning for projects...
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      16:47:29 INFO: ------------------------------------------------------------------------
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      16:47:29 INFO: Reactor Build Order:
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      16:47:29 INFO: 
      16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
      ...
      ...
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO:                                                                         
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO: ------------------------------------------------------------------------
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO: Building xxxxx
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
      16:47:29 INFO: ------------------------------------------------------------------------
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      16:47:29 INFO: 
      16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      16:47:29 INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ xxx ---
      16:47:32 Aug 27, 2013 4:47:33 PM hudson.maven.ExecutedMojo <init>
      16:47:32 WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
      16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      16:47:32 INFO: 
      16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
      

          [JENKINS-19396] Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger

          Geoff Cummings created issue -
          Geoff Cummings made changes -
          Description Original:
          After upgrading from 1.525 to 1.528 there is a lot of extra logging in our Maven build logs. This makes it hard to read the logs. It still happens in 1.529

          It is the org.apache.maven.cli.event.ExecutionEventLogger entries.

          Note:
          They are multimodule maven builds
          Timestamper plugin is active so Time is duplicated in the logs below:

          {code}
          16:47:28 Aug 27, 2013 4:47:29 PM org.apache.maven.cli.event.ExecutionEventLogger projectDiscoveryStarted
          16:47:28 INFO: Scanning for projects...
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          16:47:29 INFO: ------------------------------------------------------------------------
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          16:47:29 INFO: Reactor Build Order:
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          16:47:29 INFO:
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          ...
          ...
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO:
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO: ------------------------------------------------------------------------
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO: Building xxxxx
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO: ------------------------------------------------------------------------
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          16:47:29 INFO:
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          16:47:29 INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ xxx ---
          16:47:32 Aug 27, 2013 4:47:33 PM hudson.maven.ExecutedMojo <init>
          16:47:32 WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
          16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          16:47:32 INFO:
          16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          {code}
          New: After upgrading from 1.525 to 1.528 there is a lot of extra logging in our Maven build logs. This makes it hard to read the logs. It still happens in 1.529

          It is the org.apache.maven.cli.event.ExecutionEventLogger entries.

          Note:
          They are multimodule maven builds
          Timestamper plugin is active so Time is duplicated in the logs below:

          {code}
          16:47:28 Aug 27, 2013 4:47:29 PM org.apache.maven.cli.event.ExecutionEventLogger projectDiscoveryStarted
          16:47:28 INFO: Scanning for projects...
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          16:47:29 INFO: ------------------------------------------------------------------------
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          16:47:29 INFO: Reactor Build Order:
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          16:47:29 INFO:
          16:47:29 Aug 27, 2013 4:47:30 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
          ...
          ...
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO:
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO: ------------------------------------------------------------------------
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO: Building xxxxx
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger projectStarted
          16:47:29 INFO: ------------------------------------------------------------------------
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          16:47:29 INFO:
          16:47:29 Aug 27, 2013 4:47:31 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          16:47:29 INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ xxx ---
          16:47:32 Aug 27, 2013 4:47:33 PM hudson.maven.ExecutedMojo <init>
          16:47:32 WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
          16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          16:47:32 INFO:
          16:47:32 Aug 27, 2013 4:47:33 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
          {code}
          Summary Original: Extra org.apache.maven.cli.event.ExecutionEventLogger logging added to Maven builds makes the build log hard to read. New: Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger

          Tommy Bø added a comment -

          We noticed this after upgrading from 1.525 to 1.526. It seems that this happens in the main target in regular maven jobs. When we set up maven executions in post-build steps the log statements are fine.

          Tommy Bø added a comment - We noticed this after upgrading from 1.525 to 1.526. It seems that this happens in the main target in regular maven jobs. When we set up maven executions in post-build steps the log statements are fine.

          cowwoc added a comment -

          I am getting the following (equally hard to read) output with Maven 3.1.0, Jenkins 1.529:

          [pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects...
          

          I'm only interested in the logger message. Meaning, please trim everything up to (and including) the logger name.

          cowwoc added a comment - I am getting the following (equally hard to read) output with Maven 3.1.0, Jenkins 1.529: [pool-1-thread-1] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects... I'm only interested in the logger message. Meaning, please trim everything up to (and including) the logger name.

          Hannes Kogler added a comment -

          same here!

          upgraded from 1.518 to 1.526 today and have the same problem. Does anybody know where the additional logging entries come from?

          Hannes Kogler added a comment - same here! upgraded from 1.518 to 1.526 today and have the same problem. Does anybody know where the additional logging entries come from?

          cadiolis added a comment -

          Same here! Very irritating to have the log filled up with apparent useless information

          cadiolis added a comment - Same here! Very irritating to have the log filled up with apparent useless information

          Worksarounds appreciated. These messages make build logs very hard to read.

          Julio Morimoto added a comment - Worksarounds appreciated. These messages make build logs very hard to read.

          Per J. Lund added a comment -

          Same here. In addition it seems that the error messages is not displayed at all!
          I had to roll back to 1.523 to get a usable version.

          Per J. Lund added a comment - Same here. In addition it seems that the error messages is not displayed at all! I had to roll back to 1.523 to get a usable version.

          cowwoc added a comment -

          Agreed. Error messages are also missing for me. Someone should increase the priority of this bug.

          cowwoc added a comment - Agreed. Error messages are also missing for me. Someone should increase the priority of this bug.
          Geoff Cummings made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

            sgabriel Samuel Gabriel
            gcummings Geoff Cummings
            Votes:
            34 Vote for this issue
            Watchers:
            44 Start watching this issue

              Created:
              Updated:
              Resolved: