Steven Aerts created JENKINS-13754:
--------------------------------------

             Summary: Error when compiling a plugin against jenkins version 
1.463
                 Key: JENKINS-13754
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13754
             Project: Jenkins
          Issue Type: Bug
          Components: core, maven, plugin
    Affects Versions: current
            Reporter: Steven Aerts


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:

{code}
[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
{code}

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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to