Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: C:\Program Files\Apache Software Foundation\apache-maven-3.0.3
Java version: 1.6.0_07, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_07\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 2003", version: "5.2", arch: "x86", family: "windows"Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: C:\Program Files\Apache Software Foundation\apache-maven-3.0.3 Java version: 1.6.0_07, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_07\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 2003", version: "5.2", arch: "x86", family: "windows"
Description
When using Jenkins together with Maven and Tycho 0.13.0 version, in the console output of a build one can see detailed information about the exact cause of a compilation failure. Since upgrading to Tycho 0.15.0, when having a compilation failure, no additional info is shown in the console output. When running Maven and Tycho outside of Jenkins from command line, exact information about the compilation failure is shown and available.
The current console output from Jenkins in case of a compilation failure looks like:
message : Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.15.0:compile (default-compile) on project com.xxx: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.15.0:compile (default-compile) on project com.xxx: 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:98)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:64)
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:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure
at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:418)
at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:179)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
channel stopped
And that is all. No one could find out of that what is the real issue behind. Running Maven, Tycho again from the console to see the exact cause is quite troublesome.
Attachments
Issue Links
- is blocking
-
JENKINS-19352 Maven logs no errors
-
- Resolved
-
Code changed in jenkins
User: Nikolas Falco
Path:
src/main/java/hudson/maven/Maven3Builder.java
src/main/java/hudson/maven/util/ExecutionEventLogger.java
http://jenkins-ci.org/commit/maven-plugin/8c008c588914c16f626b236d0bebe2073b9dacc5
Log:
[FIXED JENKINS-15025]: Maven-Tycho 0.15.0 build - no additional info in
console log about compilation failure.
Restore use of hudson.maven.util.ExecutionEventLogger in the
MavenExecutionListener instance.
Now it extends the original org.apache.maven.cli.ExecutionEventLogger
and override only the enhanced mojoStarted method.
Move the logic of errors processing to main executor class
Maven3Builder.