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

NullPointerException when Maven project is configured to generate Javadoc

    Details

      Description

      If a Maven 2/3 project is configured to execute the javadoc:javadoc goal, the job fails with a NullPointerException (see below). This problem does not occur if the job is a free-style project and the Maven is executed via a "Invoke top-level Maven target" build step. While this is a possible workaround, the upstream-downstream dependency resolution is not performed (which we heavily rely on).

      We're using the Maven 3.0.2 coming with Jenkins 1.445. Version of maven-javadoc-plugin is 2.8. All of this works fine on the command line, btw.

      ===

      [JENKINS] Archiving /var/lib/jenkins/jobs/javadoc-job/workspace/pom.xml to /var/lib/jenkins/jobs/javadoc-job/modules/groupId$artifactId/builds/2012-01-09_11-06-26/archive/groupId/artifactId/2.8.0-SNAPSHOT/artifactId-2.8.0-SNAPSHOT.pom
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 7.041s
      [INFO] Finished at: Mon Jan 09 11:06:37 CET 2012
      [INFO] Final Memory: 19M/899M
      [INFO] ------------------------------------------------------------------------
      mavenExecutionResult exceptions not empty
      message : Internal error: java.lang.NullPointerException
      cause : null
      Stack trace :
      org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
      at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
      at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
      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:112)
      at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
      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: java.lang.NullPointerException
      at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
      at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
      at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
      at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
      at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
      at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
      at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
      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)
      ... 24 more
      channel stopped
      Notifying upstream projects of job completion
      Finished: FAILURE

        Issue Links

          Activity

          Show
          kutzi kutzi added a comment - https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking#IssueTracking-Whattoputinthedescriptionofanissuereport%3F
          Hide
          kutzi kutzi added a comment -

          Sorry, I missed that you had already included the Jenkins version.
          Judging by that this looks like a duplicate of JENKINS-12259

          Show
          kutzi kutzi added a comment - Sorry, I missed that you had already included the Jenkins version. Judging by that this looks like a duplicate of JENKINS-12259

            People

            • Assignee:
              Unassigned
              Reporter:
              rbarbey Robert Barbey
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: