• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • cobertura-plugin
    • None
    • Platform: All, OS: All

      When running Cobertura on a Maven project, I'm seeing a NPE - note that the
      exception is different than those of issue 2823. I've also tried 0.8.6-SNAPSHOT
      for the Cobertura plugin, which is supposed to fix 2823, but it doesn't work.
      Running with Hudson 1.296.

      My exception is:

      [INFO] Building jar:
      /home/fgiudici/Hudson/jobs/BetterBeansBinding/workspace/src/core/target/BetterBeansBinding-1.2.2-SNAPSHOT.jar
      [TASKS] Scipping maven reporter: there is already a result available.
      [INFO] Preparing cobertura:cobertura
      [WARNING] Removing: cobertura from forked lifecycle, to prevent recursive
      invocation.
      [HUDSON] Archiving
      /home/fgiudici/Hudson/jobs/BetterBeansBinding/workspace/src/core/pom.xml to
      /home/fgiudici/Hudson/jobs/BetterBeansBinding/modules/org.jdesktop.betterbeansbinding$BetterBeansBinding/builds/2009-04-09_10-18-35/archive/org.jdesktop.betterbeansbinding/BetterBeansBinding/1.2.2-SNAPSHOT/pom.xml
      [HUDSON] Archiving
      /home/fgiudici/Hudson/jobs/BetterBeansBinding/workspace/src/core/target/BetterBeansBinding-1.2.2-SNAPSHOT.jar
      to
      /home/fgiudici/Hudson/jobs/BetterBeansBinding/modules/org.jdesktop.betterbeansbinding$BetterBeansBinding/builds/2009-04-09_10-18-35/archive/org.jdesktop.betterbeansbinding/BetterBeansBinding/1.2.2-SNAPSHOT/BetterBeansBinding-1.2.2-SNAPSHOT.jar
      [INFO] ------------------------------------------------------------------------
      [ERROR] FATAL ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] null
      [INFO] ------------------------------------------------------------------------
      [INFO] Trace
      java.lang.NullPointerException
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1168)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:627)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
      at
      org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
      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 hudson.maven.agent.Main.launch(Main.java:158)
      at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
      at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:578)
      at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:524)
      at hudson.remoting.UserRequest.perform(UserRequest.java:92)
      at hudson.remoting.UserRequest.perform(UserRequest.java:46)
      at hudson.remoting.Request$2.run(Request.java:236)
      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)

          [JENKINS-3468] NPE when running Cobertura from Maven

          mdonohue added a comment -
              • Issue 3467 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 3467 has been marked as a duplicate of this issue. ***

          mdonohue added a comment -

          mdonohue added a comment - Also see http://www.nabble.com/Re%3A-Status-of-Cobertura-Plugin-issue-with-Maven--p22974277.html

          I'm trying to use Maven with Hudson with the Cobertura plugin on a nightly site
          reporting hudson job with a project with a dozen sub maven modules under a super
          pom.

          After upgrading from maven 2.0.10 to 2.1.00 and using Hudson 1.299 my nightly
          site report generation job fails with the same NPE exception. I have the
          Cobertura Hudson plugin 0.8.5 installed.

          The Cobertura web site states "You can use Cobertura from both Maven 1 and Maven
          2." But the Stephen Connolly in the thread wrote "I have not released cobertura
          with M2 project type support."

          To me these two statements conflict with each other. Its would be helpful to the
          Hudson and Maven users if the Cobertura site could state the current problems
          that were covered in the thread sited in this issue.

          If it helps, here is my stack trace:

          [INFO] Preparing cobertura:cobertura
          [HUDSON] [... text omitted for this public post...]pom.xml
          [INFO] ------------------------------------------------------------------------
          [ERROR] FATAL ERROR
          [INFO] ------------------------------------------------------------------------
          [INFO] null
          [INFO] ------------------------------------------------------------------------
          [INFO] Trace
          java.lang.NullPointerException
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1168)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:647)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
          at
          org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
          at
          org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
          at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
          at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
          at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
          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 hudson.maven.agent.Main.launch(Main.java:158)
          at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
          at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:578)
          at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:524)
          at hudson.remoting.UserRequest.perform(UserRequest.java:97)
          at hudson.remoting.UserRequest.perform(UserRequest.java:46)
          at hudson.remoting.Request$2.run(Request.java:236)
          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:619)

          jonathanjohnson added a comment - I'm trying to use Maven with Hudson with the Cobertura plugin on a nightly site reporting hudson job with a project with a dozen sub maven modules under a super pom. After upgrading from maven 2.0.10 to 2.1.00 and using Hudson 1.299 my nightly site report generation job fails with the same NPE exception. I have the Cobertura Hudson plugin 0.8.5 installed. The Cobertura web site states "You can use Cobertura from both Maven 1 and Maven 2." But the Stephen Connolly in the thread wrote "I have not released cobertura with M2 project type support." To me these two statements conflict with each other. Its would be helpful to the Hudson and Maven users if the Cobertura site could state the current problems that were covered in the thread sited in this issue. If it helps, here is my stack trace: [INFO] Preparing cobertura:cobertura [HUDSON] [... text omitted for this public post...] pom.xml [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] null [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.NullPointerException at org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1168) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:647) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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 hudson.maven.agent.Main.launch(Main.java:158) at hudson.maven.MavenBuilder.call(MavenBuilder.java:162) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:578) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:524) at hudson.remoting.UserRequest.perform(UserRequest.java:97) at hudson.remoting.UserRequest.perform(UserRequest.java:46) at hudson.remoting.Request$2.run(Request.java:236) 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:619)

          An update. I removed Cobertura from both my superpom and as a plugin from
          hudson. I get the same stack trace but now its with "Preparing
          surefire-report:report". Its really a problem with hudson and the site goal,
          plugins and lifecycle and probably with multi-level poms.

          The defect posted here http://jira.codehaus.org/browse/MNG-370 claims to have
          fixed it in 2.1.0-M1. I'm seeing this with Maven 2.1 and Hudson ver. 1.299.
          I'll add this issue reference to MNG-370.

          jonathanjohnson added a comment - An update. I removed Cobertura from both my superpom and as a plugin from hudson. I get the same stack trace but now its with "Preparing surefire-report:report". Its really a problem with hudson and the site goal, plugins and lifecycle and probably with multi-level poms. The defect posted here http://jira.codehaus.org/browse/MNG-370 claims to have fixed it in 2.1.0-M1. I'm seeing this with Maven 2.1 and Hudson ver. 1.299. I'll add this issue reference to MNG-370.

          jonathanjohnson added a comment - See also: http://jira.codehaus.org/browse/MNG-4137 http://jira.codehaus.org/browse/MNG-3704 (Please ignore the previous paste error of http://jira.codehaus.org/browse/MNG-370 )

          mdonohue added a comment -

          > After upgrading from maven 2.0.10 to 2.1.00 and using Hudson 1.299 my nightly
          site report generation job fails with the same NPE exception.

          That would be issue 2373.
          I wonder if Fabrizio is also using Maven 2.1.

          mdonohue added a comment - > After upgrading from maven 2.0.10 to 2.1.00 and using Hudson 1.299 my nightly site report generation job fails with the same NPE exception. That would be issue 2373. I wonder if Fabrizio is also using Maven 2.1.

          Yep, I'm using Maven 2.1.0

          fabriziogiudici added a comment - Yep, I'm using Maven 2.1.0

          mdonohue added a comment -

          Duplicate of issue 2372

              • This issue has been marked as a duplicate of 2372 ***

          mdonohue added a comment - Duplicate of issue 2372 This issue has been marked as a duplicate of 2372 ***

          mdonohue added a comment -

          .

          mdonohue added a comment - .

          mdonohue added a comment -

          I marked it as a dup of the wrong issue.

          This is a dup of issue 2373

              • This issue has been marked as a duplicate of 2373 ***

          mdonohue added a comment - I marked it as a dup of the wrong issue. This is a dup of issue 2373 This issue has been marked as a duplicate of 2373 ***

            stephenconnolly Stephen Connolly
            fabriziogiudici fabriziogiudici
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: