We encounter the same problem. We use maven as the only build step and at the end of an failing build, nothing is stated about the error:

27.08.2013 04:31:27 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: 
27.08.2013 04:31:27 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ JLand-Variant10000-Deployment ---
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: 
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: --- maven-resources-plugin:2.4.3:resources (default-resources) @ JLand-Variant10000-Deployment ---
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: ------------------------------------------------------------------------
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logResult
INFO: BUILD FAILURE
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: ------------------------------------------------------------------------
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Total time: 2.797s
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Finished at: Tue Aug 27 04:31:28 CEST 2013
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger logStats
INFO: Final Memory: 6M/123M
27.08.2013 04:31:28 org.apache.maven.cli.event.ExecutionEventLogger sessionEnded
INFO: ------------------------------------------------------------------------
[JENKINS] Archiving [...]
Warte bis Jenkins die Datensammlung abgeschlossen hat
channel stopped
Finished: FAILURE

The behavior appears on compile errors as well as on other goals, i.e. cargo:deploy.

Environment:

• Microsoft Windows Server 2003 R2 SP2
• Maven 3.0.3

If you use a freestyle project the logging is as expected.

I looked at the difference in the way Maven is started between the Maven project and a freestyle project, and it looks like for a Maven project Maven is started in a forked java process, like below:

/u01/appl/jenkins/tools/hudson.model.JDK/Sun_JDK_1.6u45/bin/java -Dorg.slf4j.simpleLogger.showThreadName=false -Dorg.slf4j.simpleLogger.showDateTime=false -Dorg.slf4j.simpleLogger.levelInBrackets=true -Dorg.slf4j.simpleLogger.showLogName=false -Djava.awt.headless=true -cp /u01/appl/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.4.jar:/u01/appl/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.0/boot/plexus-classworlds-2.4.2.jar:/u01/appl/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.0/conf/logging jenkins.maven3.agent.Maven31Main /u01/appl/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.0 /var/cache/jenkins/war/WEB-INF/lib/remoting-2.32.jar /u01/appl/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.4.jar /u01/appl/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 40757
11:10:18 <===[JENKINS REMOTING CAPACITY]===>channel started
11:10:19 log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
11:10:19 log4j:WARN Please initialize the log4j system properly.
11:10:20 Executing Maven: -B -f /u01/appl/jenkins/jobs/upc-generic/workspace/pom.xml -e clean install

The maven error is probably written to stderr, and probably this is not redirected to jenkins.

What changed in 1.526 to cause this and can it be reverted? Kind of makes Maven builds useless if you can't see why they failed. I tried the freestyle project and would consider switching, but the Sonar plugin fails to launch because the mvn command is not in the default path and it doesn't seem to honor the path used for the main build. I don't want to jump through hoops for 70 Maven jobs...sigh.

Hi. Having exactly the same problem on Windows 7 and Jenkins 1.530. Maven (3.0.4) build fails with no output in Jenkins (even if using -X). (Standalone Maven build works fine from command line)

Started seeing this after upgrade to 1.531 (from 1.521?) in a CentOS6 Linux environment.

Before, I have the full traceback

message : Failed to execute goal on project example-project: Could not resolve dependencies for project ... etc ...

After, I only have this one line cluing me in to which module failed:

INFO: example-project ...................... FAILURE [3.910s]

FWIW, I've managed to get back to a working setup with Jenkins 1.531 and Maven Project Plugin at 1.522 (haven't tried other plugin versions, this just happened to be what was available to me).

Possibly related to JENKINS-15935. At least there were a lot of changes to the maven plugin in 1.526 due to that issue