-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 1.528
-
-
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
- causes
-
JENKINS-72976 Extra logging added to console log on Maven builds and prevent Error-Prone parsing
-
- Closed
-
- is related to
-
JENKINS-15935 Can't build using maven 3.1.0
-
- Resolved
-
-
JENKINS-19352 Maven logs no errors
-
- Resolved
-
- links to
[JENKINS-19396] Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
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 |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
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.