Details
-
Bug
-
Status: Reopened (View Workflow)
-
Minor
-
Resolution: Unresolved
-
Jenkins 1.528
Description
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
Attachments
Issue Links
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
Activity
cowwoc
added a comment - @Daniel Beck,
Sorry, the last comment was directed at you. I am getting a very verbose syntax:
[pool-3-thread-1] INFO org.apache.maven.cli.transfer.Slf4jMavenTransferListener - Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom
It looks like the logging pattern is at fault. I am expecting the line to begin with "Downloading". Is there any way to make it less verbose?
cowwoc
added a comment - @Daniel Beck,
Sorry, the last comment was directed at you. I am getting a very verbose syntax:
[pool-3-thread-1] INFO org.apache.maven.cli.transfer.Slf4jMavenTransferListener - Downloading: http: //repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom
It looks like the logging pattern is at fault. I am expecting the line to begin with "Downloading". Is there any way to make it less verbose? 
Kent Granström
added a comment - Reopen by mistake This issue still occur when running master on windows and slaves on linux with maven plugin version 3.8. The culprit is line https://github.com/jenkinsci/maven-plugin/blob/8adb97e92fbf0af494c26cc64611bd648b6ae8e9/src/main/java/hudson/maven/Maven31ProcessFactory.java#L66 which is also found in Maven32ProcessFactory Maven33ProcessFactory and Maven35ProcessFactory
The problem is mvn.getHomeDir().getPath() is running on master which uses windows and the file path become \home\jenkins\tools... maven cp becomes
-cp /home/jenkins/maven35-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3/boot/plexus-classworlds-2.6.0.jar:\home\jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven-3.6.3/conf/logging jenkins.maven3.agent.Maven35Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3 /home/jenkins/remoting.jar /home/jenkins/maven35-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 40073
this can be easily corrected by changing the line to
path += (getLauncher().isUnix()?":":";") + mvn.getHome() + "/conf/logging";
mvn.getHome() is a string with the correct path separator.
Samuel Gabriel
added a comment - - edited This issue still occur when running master on windows and slaves on linux with maven plugin version 3.8. The culprit is line https://github.com/jenkinsci/maven-plugin/blob/8adb97e92fbf0af494c26cc64611bd648b6ae8e9/src/main/java/hudson/maven/Maven31ProcessFactory.java#L66 which is also found in Maven32ProcessFactory Maven33ProcessFactory and Maven35ProcessFactory
The problem is mvn.getHomeDir().getPath() is running on master which uses windows and the file path become \home\jenkins\tools... maven cp becomes
-cp /home/jenkins/maven35-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3/boot/plexus-classworlds-2.6.0.jar :\home\jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven-3.6.3/ conf/logging jenkins.maven3.agent.Maven35Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven-3.6.3 /home/jenkins/remoting.jar /home/jenkins/maven35-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 40073
this can be easily corrected by changing the line to
path += (getLauncher().isUnix()? ":" : ";" ) + mvn.getHome() + "/conf/logging" ;
mvn.getHome() is a string with the correct path separator. Samuel Gabriel
added a comment - I created this pull request in order to fix the issue
https://github.com/jenkinsci/maven-plugin/pull/191 
@Christian,
I have the Maven Integration plugin 2.2 installed, and I'm still seeing org.apache.maven.cli.event.ExecutionEventLogger everywhere. Shouldn't this issue be reopened?