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
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. 
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. 
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.
The difference is that Maven 3 correctly computes the transitive classpath of the processor libraries, whereas Maven 2 omits jsr305-1.3.9.jar and guava-12.0-rc1.jar. This is probably the standard failure of Maven 2 to handle transitive dependencies properly (https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution). The problem exists also when using JDK 7, but javac in that version seems to just give up early on running annotation processors.
Best is to use Maven 3. If you must use Maven 2, the workaround is to add to your POM:
<dependencies> <dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>12.0-rc1</version> <scope>provided</scope> </dependency> </dependencies>
Leaving open since there is not an obvious connection between the bug symptom and problem; if an automatic workaround cannot be found for Maven 2 users, may be best to just add a declaration to the POM in the HPI archetype requesting Maven 3.
I also encountered this error trying to run tests from Intellij Idea. Proposed workaround didn't helped
Ari Hyttinen
added a comment - Also encountered here (using Maven 2, Netbeans 6.9.1) when using parent version 1.466, fixed by switching to an older parent version.
Ari Hyttinen
added a comment - Also encountered here (using Maven 2, Netbeans 6.9.1) when using parent version 1.466, fixed by switching to an older parent version. Workaround of adding deps to POM resolved the problem (Maven 2.2.1 & Java 6). Better if someone could update HPI to include this in the POM.
Kamal Mettananda
added a comment - - edited Workaround of adding deps to POM resolved the problem (Maven 2.2.1 & Java 6). Better if someone could update HPI to include this in the POM. Would rather not leave Maven 2 workarounds in every plugin, especially as this dependency could easily be rendered stale by a core update.
Perhaps put an enforcer rule in the archetypal POM requiring Maven 3.0.4+, but with a comment linking to this issue explaining how you can make it work on Maven 2 if you need to.
I had the same issue with IntelliJ. In my case, from the project setting, "Compiler > Annotation Processors > Enable annotation processing" fixed the problem (but I don't know why.)
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/pom.xml
maven-plugin/pom.xml
http://jenkins-ci.org/commit/jenkins/abeebce2230c37c1ad6bd6b5d5af615859980568
Log:
[FIXED JENKINS-13754]
while I can't pinpoint what's really causing this, moving this
dependency to core seems to solve the problem.
Guava is defined as dependency in org.kohsuke.stapler:stapler, then
redefined to a newer version in maven-plugin. The latter gets to plugins
as a test scope. When I look at the dependency scope of this in a plugin
project in IntelliJ IDEA, it reports this dependency as the test scope
(and this makes the error somewhat understandable.)
Integrated in 
jenkins_main_trunk #2041
[FIXED JENKINS-13754] (Revision abeebce2230c37c1ad6bd6b5d5af615859980568)
Result = SUCCESS
kohsuke : abeebce2230c37c1ad6bd6b5d5af615859980568
Files :
- core/pom.xml
- maven-plugin/pom.xml
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
pom.xml
http://jenkins-ci.org/commit/maven-plugin/56cf6e330d7165e714238b14510521c2ab8880ee
Log:
[FIXED JENKINS-13754]
while I can't pinpoint what's really causing this, moving this
dependency to core seems to solve the problem.
Guava is defined as dependency in org.kohsuke.stapler:stapler, then
redefined to a newer version in maven-plugin. The latter gets to plugins
as a test scope. When I look at the dependency scope of this in a plugin
project in IntelliJ IDEA, it reports this dependency as the test scope
(and this makes the error somewhat understandable.)
Originally-Committed-As: abeebce2230c37c1ad6bd6b5d5af615859980568
We've also seen this when we tried version 1.465. Definitely would be nice to have fixed. Thanks!