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

Maven jobs don't report all details of failures

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • maven-plugin
    • None
    • Jenkins 1.420 but I'm almost sure to have see it before

      I have a maven build which is failing because of compilation error.
      My local Maven (3.0.3) build returns this :

      [INFO] ------------------------------------------------------------------------
[INFO] Building eXo Social Portlet Web App 1.2.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
Downloading: http://repository.exoplatform.org/private/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
Downloaded: http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml (2 KB at 0.0 KB/sec)
Downloading: http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom
Downloaded: http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom (3 KB at 4.2 KB/sec)
Downloading: http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar
Downloaded: http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar (35 KB at 52.6 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ exo.social.webapp.portlet ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-plugin-versions) @ exo.social.webapp.portlet ---
[WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks.
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @ exo.social.webapp.portlet ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @ exo.social.webapp.portlet ---
[INFO] 
[INFO] --- maven-resources-plugin:2.4.1:resources (default-resources) @ exo.social.webapp.portlet ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ exo.social.webapp.portlet ---
[INFO] Compiling 28 source files to /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
......
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:58.991s
[INFO] Finished at: Thu Jul 14 14:30:36 CEST 2011
[INFO] Final Memory: 25M/125M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project exo.social.webapp.portlet: Compilation failure: Compilation failure:
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIHomeSpacePortlet.java:[64,36] [deprecation] hasEditPermission(org.exoplatform.social.core.space.model.Space,java.lang.String) in org.exoplatform.social.core.space.spi.SpaceService has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UISocialLogoPortlet.java:[104,13] [deprecation] getOrCreateIdentity(java.lang.String,java.lang.String) in org.exoplatform.social.core.manager.IdentityManager has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIMembersPortlet.java:[224,44] [deprecation] getOrCreateIdentity(java.lang.String,java.lang.String) in org.exoplatform.social.core.manager.IdentityManager has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIMembersPortlet.java:[236,44] [deprecation] getOrCreateIdentity(java.lang.String,java.lang.String) in org.exoplatform.social.core.manager.IdentityManager has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UISpacesToolBarPortlet.java:[91,21] cannot find symbol
[ERROR] symbol  : constructor GenericScope(int)
[ERROR] location: class org.exoplatform.portal.mop.navigation.GenericScope
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UISpacesToolBarPortlet.java:[106,42] [deprecation] getAccessibleSpaces(java.lang.String) in org.exoplatform.social.core.space.spi.SpaceService has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIProfileNavigationPortlet.java:[122,36] [deprecation] invite(org.exoplatform.social.core.identity.model.Identity,org.exoplatform.social.core.identity.model.Identity) in org.exoplatform.social.core.manager.RelationshipManager has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIProfileNavigationPortlet.java:[144,36] [deprecation] confirm(org.exoplatform.social.core.relationship.model.Relationship) in org.exoplatform.social.core.manager.RelationshipManager has been deprecated
[ERROR] 
[ERROR] /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIProfileNavigationPortlet.java:[167,36] [deprecation] remove(org.exoplatform.social.core.relationship.model.Relationship) in org.exoplatform.social.core.manager.RelationshipManager has been deprecated
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :exo.social.webapp.portlet

      Now the same build in jenkins with a maven jobs gives this output (https://ci.exoplatform.org/job/social-1.2.x-ci/3/consoleText) :

      [INFO] ------------------------------------------------------------------------
[INFO] Building eXo Social Portlet Web App 1.2.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repository.exoplatform.org/content/groups/ci/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
Downloaded: http://repository.exoplatform.org/content/groups/ci/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml (2 KB at 0.1 KB/sec)
Downloading: http://repository.exoplatform.org/content/groups/ci/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom
Downloaded: http://repository.exoplatform.org/content/groups/ci/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom (3 KB at 24.0 KB/sec)
Downloading: http://repository.exoplatform.org/content/groups/ci/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar
Downloaded: http://repository.exoplatform.org/content/groups/ci/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar (35 KB at 40.5 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ exo.social.webapp.portlet ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-plugin-versions) @ exo.social.webapp.portlet ---
[WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks.
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @ exo.social.webapp.portlet ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @ exo.social.webapp.portlet ---
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.0-beta-4:create (default) @ exo.social.webapp.portlet ---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd /home/swfhudson/data/jobs/social-1.2.x-ci/workspace/sources/webapp/portlet && svn --non-interactive info
[INFO] Working directory: /home/swfhudson/data/jobs/social-1.2.x-ci/workspace/sources/webapp/portlet
[INFO] Storing buildNumber: 71394 at timestamp: 1310643076202
[INFO] Executing: /bin/sh -c cd /home/swfhudson/data/jobs/social-1.2.x-ci/workspace/sources/webapp/portlet && svn --non-interactive info
[INFO] Working directory: /home/swfhudson/data/jobs/social-1.2.x-ci/workspace/sources/webapp/portlet
[INFO] Storing buildScmBranch: branches/1.2.x/webapp/portlet
[INFO] 
[INFO] --- maven-resources-plugin:2.4.1:resources (default-resources) @ exo.social.webapp.portlet ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ exo.social.webapp.portlet ---
[INFO] Compiling 28 source files to /home/swfhudson/data/jobs/social-1.2.x-ci/workspace/sources/webapp/portlet/target/classes
mojoFailed org.apache.maven.plugins:maven-compiler-plugin:2.0.2(default-compile)
projectFailed org.exoplatform.social:exo.social.webapp.portlet:1.2.1-SNAPSHOT
[JENKINS] Archiving /home/swfhudson/data/jobs/social-1.2.x-ci/workspace/sources/webapp/portlet/pom.xml to /home/swfhudson/data/jobs/social-1.2.x-ci/modules/org.exoplatform.social$exo.social.webapp.portlet/builds/2011-07-14_13-21-24/archive/org.exoplatform.social/exo.social.webapp.portlet/1.2.1-SNAPSHOT/exo.social.webapp.portlet-1.2.1-SNAPSHOT.pom
sessionEnded
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
....
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9:54.922s
[INFO] Finished at: Thu Jul 14 13:31:22 CEST 2011
[INFO] Final Memory: 96M/1123M
[INFO] ------------------------------------------------------------------------
maven builder waiting
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project exo.social.webapp.portlet: Compilation failure
cause : Compilation failure
Stack trace : 
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project exo.social.webapp.portlet: Compilation failure
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
	at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:126)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:73)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:287)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
	at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
	at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
	... 27 more
Maven failed with error.

      I though this issue was already opened but I didn't find it. I found the one about logs issues and errors reporting in POMs parsing but not in the build itself. I don't know if it is related.
      I mark this issue as critical as it makes maven jobs and jenkins pretty useless if it doesn't report to developers the origin of the problem it discovers

        1. compilefailure.zip
          3 kB

          [JENKINS-10333] Maven jobs don't report all details of failures

          Dave Riches added a comment -

          I'm seeing something very similar with Maven-based builds.

          Jenkins version is 1.421, Maven compiler plugin version is 2.0.1, jdk is 1.6, update 20.

          Error output is:

          maven builder waiting
          mavenExecutionResult exceptions not empty
          message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile (default-compile) on project rts-att-adapter: Compilation failure
          cause : Compilation failure
          Stack trace :
          org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile (default-compile) on project rts-att-adapter: Compilation failure
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
          at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
          at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
          at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
          at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
          at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
          at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
          at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
          at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
          at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
          at hudson.maven.Maven3Builder.call(Maven3Builder.java:126)
          at hudson.maven.Maven3Builder.call(Maven3Builder.java:73)
          at hudson.remoting.UserRequest.perform(UserRequest.java:118)
          at hudson.remoting.UserRequest.perform(UserRequest.java:48)
          at hudson.remoting.Request$2.run(Request.java:287)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
          at java.util.concurrent.FutureTask.run(FutureTask.java:138)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:619)
          Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
          at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
          at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
          at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
          at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
          ... 27 more

          Dave Riches added a comment - I'm seeing something very similar with Maven-based builds. Jenkins version is 1.421, Maven compiler plugin version is 2.0.1, jdk is 1.6, update 20. Error output is: maven builder waiting mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile (default-compile) on project rts-att-adapter: Compilation failure cause : Compilation failure Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile (default-compile) on project rts-att-adapter: Compilation failure at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:126) at hudson.maven.Maven3Builder.call(Maven3Builder.java:73) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) ... 27 more

          Tim Drury added a comment -

          I get the same error on Jenkins 1.450 compiling a maven 3.0.4 project. This just started happening on our Jenkins system and it correlates to our move from maven 2.2.1 to maven 3.0.4, but I could swear we got good compilation error messages even with 3.0.4. The compiler plugin is 2.0.2.

          Tim Drury added a comment - I get the same error on Jenkins 1.450 compiling a maven 3.0.4 project. This just started happening on our Jenkins system and it correlates to our move from maven 2.2.1 to maven 3.0.4, but I could swear we got good compilation error messages even with 3.0.4. The compiler plugin is 2.0.2.

          Andreas Sandberg added a comment -

          I had the same problem solved by using a newer version (2.3.2 instead of 2.0.2) of the maven compile plugin (specified in the pom or in your parent pom).

          This also seems to be an duplicate of Jira Issue: 12858.

          https://issues.jenkins-ci.org/browse/JENKINS-12858

          Andreas Sandberg added a comment - I had the same problem solved by using a newer version (2.3.2 instead of 2.0.2) of the maven compile plugin (specified in the pom or in your parent pom). This also seems to be an duplicate of Jira Issue: 12858. https://issues.jenkins-ci.org/browse/JENKINS-12858

          Federico Paolantoni added a comment -

          Same issue with jenkins 1.447.2, maven 3.0.2 and plugin version 2.0.2. There is some relation between the plugin and jenkins. Because in other environment, running build from cli, the console output shows the correct error log.

          Federico Paolantoni added a comment - Same issue with jenkins 1.447.2, maven 3.0.2 and plugin version 2.0.2. There is some relation between the plugin and jenkins. Because in other environment, running build from cli, the console output shows the correct error log.

          Sebastien Arod added a comment -

          Same issue with jenkins 1.466.1, and maven 3.0.4

          The only way I found to get the error message in jenkins log is to use "-e -X" maven parameters but it produces a VERY VERY verbose log.
          The erro can then be found after "[DEBUG] Original compiler output:"

          Sebastien Arod added a comment - Same issue with jenkins 1.466.1, and maven 3.0.4 The only way I found to get the error message in jenkins log is to use "-e -X" maven parameters but it produces a VERY VERY verbose log. The erro can then be found after " [DEBUG] Original compiler output:"

          Marcelo Rebasti added a comment -

          This is a compatibility issue between maven 3 and maven-compiler-plugin. In order to get the error messages using maven in embedded mode, you have to use maven-compiler-plugin version 2.3.2 or higher.

          Regards.

          Marcelo Rebasti

          Marcelo Rebasti added a comment - This is a compatibility issue between maven 3 and maven-compiler-plugin. In order to get the error messages using maven in embedded mode, you have to use maven-compiler-plugin version 2.3.2 or higher. Regards. Marcelo Rebasti

          tao tao added a comment - - edited

          Hey Marcelo, I'm using jenkins 1.537, maven verioned 3.0.4, and I've tried your way to update the maven-compiler-plugin to 3.1, now I can see the error message on the screen, but it doesn't contain the trace stack. I have to add -e parameters to see the details. So can you tell me how to fix that? Thanks.

          tao tao added a comment - - edited Hey Marcelo, I'm using jenkins 1.537, maven verioned 3.0.4, and I've tried your way to update the maven-compiler-plugin to 3.1, now I can see the error message on the screen, but it doesn't contain the trace stack. I have to add -e parameters to see the details. So can you tell me how to fix that? Thanks.

          Marcelo Rebasti added a comment -

          Test project with compile errors.

          Marcelo Rebasti added a comment - Test project with compile errors.

          Marcelo Rebasti added a comment -

          Tao,

          When a build fails with compile errors, maven3 don't show any stacktrace unless you use the -e parameter. If you try compile the project from the command line, you'll see the same message than jenkins shows.

          For example, when I try to compile the project "compilefailure" (attached to this issue) from command line and jenkins, I obtain these messages:

          ==================== Command Line ===============================
          [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ compilefailure —
          [INFO] Changes detected - recompiling the module!
          [INFO] Compiling 1 source file to /home/marcelo/dev/repo/compilefailure/target/classes
          [INFO] -------------------------------------------------------------
          [ERROR] COMPILATION ERROR :
          [INFO] -------------------------------------------------------------
          [ERROR] /home/marcelo/dev/repo/compilefailure/src/main/java/org/marcelo/App.java:[12,9] cannot find symbol
          symbol: variable BadClass
          location: class org.marcelo.App
          [INFO] 1 error
          [INFO] -------------------------------------------------------------
          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD FAILURE
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 2.973s
          [INFO] Finished at: Tue Oct 29 08:27:53 ART 2013
          [INFO] Final Memory: 14M/131M
          [INFO] ------------------------------------------------------------------------
          [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project compilefailure: Compilation failure
          [ERROR] /home/marcelo/dev/repo/compilefailure/src/main/java/org/marcelo/App.java:[12,9] cannot find symbol
          [ERROR] symbol: variable BadClass
          [ERROR] location: class org.marcelo.App
          [ERROR] -> [Help 1]
          [ERROR]
          [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
          [ERROR] Re-run Maven using the -X switch to enable full debug logging.
          [ERROR]
          [ERROR] For more information about the errors and possible solutions, please read the following articles:
          [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

          ==================== Jenkins ===============================
          [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ compilefailure —
          [INFO] Changes detected - recompiling the module!
          [INFO] Compiling 1 source file to /home/marcelo/dev/repo/maven-plugin/work/workspace/compilefailure/target/classes

          [INFO] -------------------------------------------------------------
          [ERROR] COMPILATION ERROR :
          [INFO] -------------------------------------------------------------
          [ERROR] /home/marcelo/dev/repo/maven-plugin/work/workspace/compilefailure/src/main/java/org/marcelo/App.java:[12,9] cannot find symbol
          symbol: variable BadClass
          location: class org.marcelo.App
          [INFO] 1 error
          [INFO] -------------------------------------------------------------

          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD FAILURE
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 5.302s
          [INFO] Finished at: Tue Oct 29 08:35:13 ART 2013
          [INFO] Final Memory: 18M/130M
          [INFO] ------------------------------------------------------------------------
          [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project compilefailure: Compilation failure
          [ERROR] /home/marcelo/dev/repo/maven-plugin/work/workspace/compilefailure/src/main/java/org/marcelo/App.java:[12,9] cannot find symbol
          [ERROR] symbol: variable BadClass
          [ERROR] location: class org.marcelo.App
          [ERROR] -> [Help 1]
          [ERROR]
          [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
          [ERROR] Re-run Maven using the -X switch to enable full debug logging.
          [ERROR]
          [ERROR] For more information about the errors and possible solutions, please read the following articles:
          [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
          ====================== End of logs ================================

          As you can see, both logs are identical.

          If you are talking about other case, please fill a new bug with the description, and I'll try to reproduce it.

          Regards.

          Marcelo Rebasti

          Marcelo Rebasti added a comment - Tao, When a build fails with compile errors, maven3 don't show any stacktrace unless you use the -e parameter. If you try compile the project from the command line, you'll see the same message than jenkins shows. For example, when I try to compile the project "compilefailure" (attached to this issue) from command line and jenkins, I obtain these messages: ==================== Command Line =============================== [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ compilefailure — [INFO] Changes detected - recompiling the module! [INFO] Compiling 1 source file to /home/marcelo/dev/repo/compilefailure/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /home/marcelo/dev/repo/compilefailure/src/main/java/org/marcelo/App.java: [12,9] cannot find symbol symbol: variable BadClass location: class org.marcelo.App [INFO] 1 error [INFO] ------------------------------------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.973s [INFO] Finished at: Tue Oct 29 08:27:53 ART 2013 [INFO] Final Memory: 14M/131M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project compilefailure: Compilation failure [ERROR] /home/marcelo/dev/repo/compilefailure/src/main/java/org/marcelo/App.java: [12,9] cannot find symbol [ERROR] symbol: variable BadClass [ERROR] location: class org.marcelo.App [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException ==================== Jenkins =============================== [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ compilefailure — [INFO] Changes detected - recompiling the module! [INFO] Compiling 1 source file to /home/marcelo/dev/repo/maven-plugin/work/workspace/compilefailure/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /home/marcelo/dev/repo/maven-plugin/work/workspace/compilefailure/src/main/java/org/marcelo/App.java: [12,9] cannot find symbol symbol: variable BadClass location: class org.marcelo.App [INFO] 1 error [INFO] ------------------------------------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.302s [INFO] Finished at: Tue Oct 29 08:35:13 ART 2013 [INFO] Final Memory: 18M/130M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project compilefailure: Compilation failure [ERROR] /home/marcelo/dev/repo/maven-plugin/work/workspace/compilefailure/src/main/java/org/marcelo/App.java: [12,9] cannot find symbol [ERROR] symbol: variable BadClass [ERROR] location: class org.marcelo.App [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException ====================== End of logs ================================ As you can see, both logs are identical. If you are talking about other case, please fill a new bug with the description, and I'll try to reproduce it. Regards. Marcelo Rebasti

          tao tao added a comment -

          Hi Marcelo,

          Thanks a lot for your helpful response, you've solved my question, and now I can always use -e appending to the command line to look at the full error log with stack trace.

          tao tao added a comment - Hi Marcelo, Thanks a lot for your helpful response, you've solved my question, and now I can always use -e appending to the command line to look at the full error log with stack trace.

            Unassigned Unassigned
            aheritier Arnaud Héritier
            Votes:
            10 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: