Major While investigating a plugin issue which was introduced with version 1.463 of jenkins I found out that it is impossible to build any plugin against this version.
Even the default plugin generated by mvn hpi:create does not build anymore, after you select 1.463 in the pom.xml.
The build fails with the following exception:
[INFO] Compiling 1 source file to /home/steven/tmp/test/test/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] error: Exception thrown while constructing Processor object: com/google/common/collect/Multimap [INFO] 1 error [INFO] ------------------------------------------------------------- [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure error: Exception thrown while constructing Processor object: com/google/common/collect/Multimap [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure error: Exception thrown while constructing Processor object: com/google/common/collect/Multimap at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure error: Exception thrown while constructing Processor object: com/google/common/collect/Multimap at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more
I am not a mvn expert but adding the latests guava.jar to the classpath of the javac fixes the problem.
I assume that this problem was introduced in version 1.463 as it does not exist in 1.462.
[JENKINS-13754] Error when compiling a plugin against jenkins version 1.463
Steven Aerts
created issue -
Steven Aerts
added a comment - My pull request has been accepted and integrated in the latest version of the klocwork plugin.
So closing this bug.
Steven Aerts
added a comment - My pull request has been accepted and integrated in the latest version of the klocwork plugin .
So closing this bug. Steven Aerts
added a comment - My pull request has been accepted, merged and released. So closing this bug.
Steven Aerts
added a comment - My pull request has been accepted, merged and released. So closing this bug. Steven Aerts
made changes -
| Assignee | New: Steven Aerts [ steven_aerts ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Holger Mense
added a comment - I am reopening this issue, because I think it has been accidentally closed by Steven Aerts. His patch does not have any connection to this issue and SCM comment also mentions another issue (13743), which is still opened.
Furthermore, I am also seeing the original problem with Jenkins 1.473, when trying to build the PTC Integrity Plugin.
Holger Mense
added a comment - I am reopening this issue, because I think it has been accidentally closed by Steven Aerts. His patch does not have any connection to this issue and SCM comment also mentions another issue (13743), which is still opened.
Furthermore, I am also seeing the original problem with Jenkins 1.473, when trying to build the PTC Integrity Plugin. Holger Mense
made changes -
| Assignee | Original: Steven Aerts [ steven_aerts ] | |
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Shai Ben-Hur
added a comment - Also an issue in Jenkins 1.475 Reproducible for me only when building with JDK 6 and Maven 2; works when using JDK 7 and/or Maven 3.
| Labels | Original: build jenkins maven plugin | New: build jdk maven plugin |
We've also seen this when we tried version 1.465. Definitely would be nice to have fixed. Thanks!