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.

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.

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?

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.

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.

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

Same here! Does anyone have a workaround for latest version?

I had to roll back to 1.525 to solve this problem

Separate issue exists for missing errors: JENKINS-19352

Possibly related (or even caused by): JENKINS-15935

Can others confirm that this is still happening in 1.529+?
The changelog mentions that this was fixed in 1.529 http://jenkins-ci.org/changelog

@kutzi, I already did. See https://issues.jenkins-ci.org/browse/JENKINS-19396?focusedCommentId=184739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-184739

@cowwoc I did see that, but it's not clear for me if you're seeing the same problem reported originally (i.e. duplicated log entries) or some other related issue

@kutzi This issue is still present in Jenkins 1.531's Maven 3.0 builds. The changelog entry you mentioned must be about a different, Maven 3.1 related issue.

I can also confirm that this is still happening in 1.532 (Maven 3.0 builds).

Same happened on Jenkins v. 1.533 with Maven 2/3 jobs

Is there some logger configuration that I am missing in my setup?
Something that changed since 1.523?
The versions between 1.524-1.533 are completely useless to us.
All error messages from maven are lost and it is impossible to see what caused a build to fail.
The output is flooded with useless log and important info is not even shown.
We will have to stay with 1.523 until this is fixed.

Sorry for my frustration - I like, and depend on a great product like Jenkins!

@ Per : you can see from the discussion there is a bug not fixed that causes all this problems. Try v 1.522. I made a revert back to that one myself. We all are waiting for this bug to get fixed

Workaround: add -Djava.util.logging.SimpleFormatter.format="%4$s: %5$s%6$s%n" to the MAVEN_OPTS of the affected jobs

Code changed in jenkins
User: Christoph Kutzinski
Path:
src/main/java/hudson/maven/MavenModuleSetBuild.java
http://jenkins-ci.org/commit/maven-plugin/11b05a7615a43902b5577782b415aa5befa9121d
Log:
[FIXED JENKINS-19396] use less verbose logging format for Maven 3 builds

Would be great if someone could try the fixed maven-plugin before I cut a release from it:
https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp

Hi, just installed the plugin and got a clean log.
Also, i notice at the begginning of the console output the additional maven opt "-Djava.util.logging.SimpleFormatter.format=%4$s: %5$s%6$s%n"
+1

Works with current Jenkins 1.534. The added lines no longer appear.

Hi,

This fixes it for builds using JDK 7 but not for builds using JDK 6

thanks
Geoff

From what I can tell, the java.util.logging.SimpleFormatter.format property feature was introduced in Java 7. Still have extra logging for maven builds using Java 6

@Geoff, thanks for the feedback. Seems you're right - the property was added in Java 7.
I'll try to find a way to fix this for Java 6, too.

BTW: I'm open for pull requests, if someone has a clever solution

Still seeing this in 1.535 (JDK 7)

I just uploaded a test build which should fix the issue for JDK 6, too
https://www.dropbox.com/sh/kjkh5g3r68kmlj7/JvgKJnf7gp
Please test

Code changed in jenkins
User: Christoph Kutzinski
Path:
src/main/java/hudson/maven/Maven3Builder.java
src/main/java/hudson/maven/MavenConsoleFormatter.java
src/main/java/hudson/maven/MavenModuleSetBuild.java
http://jenkins-ci.org/commit/maven-plugin/d8862d4ee8585411b6a46ce1101000962cc4bcb0
Log:
[FIXED JENKINS-19396] use less verbose logging format for Maven 3 builds

Working great in Jenkins 1.535!!

thanks very much !!

Geoff, Java 6 and/or Java 7?

Code changed in jenkins
User: Christoph Kutzinski
Path:
src/main/java/hudson/maven/Maven3Builder.java
src/main/java/hudson/maven/Maven3ConsoleFormatter.java
src/main/java/hudson/maven/MavenConsoleFormatter.java
http://jenkins-ci.org/commit/maven-plugin/035d780980c316dc25cc656bd18d302172bc78d5
Log:
JENKINS-19396 Maven3ConsoleFormatter shouldn't be public, so it doesn't become part of the API. Plus: added license

Oh Java 6 is what I was using.

I forgot to test with Java 7, I'll check that tomorrow morning

The issue is still there in v1.535 with a multi-module build where the top-level POM and one of the other Maven projects is useing:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-toolchains-plugin</artifactId>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>toolchain</goal>
</goals>
</execution>
</executions>
<configuration>
<toolchains>
<jdk>
<version>1.8</version>
<vendor>oracle</vendor>
</jdk>
</toolchains>
</configuration>
</plugin>

and

java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-b111)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b53, mixed mode)

There seem to be patches after v1.535

Is this already fixed?

@puce the Maven plugin is now independent, not tied to a specific Jenkins version.

Is this going to be backported to LTS? I'm running into the same problem with 1.509.4

aldaris: 1.509.x is obsolete. 1.532.1 has been released two weeks ago (nobody bothered to update the web site though), which seems to include the fix.

Thanks for the heads up, I've completely missed that release.

With Jenkins ver. 1.532.1, we still get too many of these entries:

Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
INFO: ------------------------------------------------------------------------
Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
INFO: Reactor Build Order:
Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
INFO:
Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted
INFO:

Christian Eichenberger: Update Maven Plugin to version 2.0. It's now independent of the core version.

@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?

@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?

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.

I created this pull request in order to fix the issue 

https://github.com/jenkinsci/maven-plugin/pull/191