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

I am not able to build with maven2 module due to NPE

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      I think this might have something to do with how I have configured my poms for
      <ciManagement>. I have several levels in the child pom hiearchy and Only
      specify the ci system in the top level and then change the notifiers in the
      children. If I put them into a single project it works. For example, let's
      assume the following strutcture:

      top
      child1
      child2
      grandchild21

      In top's pom.xml, I configure the following:

      <ciManagement>
      <system>hudson</system>
      <url>http://myHudsonBox/hudson</url>
      </ciManagement>

      In child1 and child2, I have the following:

      <ciManagement>
      <notifiers>
      <notifier>
      <type>mail</type>
      <sendOnError>true</sendOnError>
      <sendOnFailure>true</sendOnFailure>
      <sendOnWarning>true</sendOnWarning>
      <sendOnSuccess>true</sendOnSuccess>
      <configuration>
      <address>jason_chaffee@tvworks.com</address>
      </configuration>
      </notifier>
      </notifiers>
      </ciManagement>

      I get the following error:

      Parsing POMs
      ERROR: Processing failed due to a bug in the code. Please report thus to
      users@hudson.dev.java.net
      java.lang.NullPointerException
      at hudson.maven.PomInfo.<init>(PomInfo.java:93)
      at
      hudson.maven.MavenModuleSetBuild$PomParser.toPomInfo(MavenModuleSetBuild.java:311)
      at
      hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:295)
      at
      hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:258)
      at hudson.FilePath.act(FilePath.java:239)
      at
      hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:193)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:121)
      at hudson.model.Run.run(Run.java:559)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:132)
      at hudson.model.Executor.run(Executor.java:59)
      FATAL: null
      java.lang.NullPointerException
      at hudson.maven.PomInfo.<init>(PomInfo.java:93)
      at
      hudson.maven.MavenModuleSetBuild$PomParser.toPomInfo(MavenModuleSetBuild.java:311)
      at
      hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:295)
      at
      hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:258)
      at hudson.FilePath.act(FilePath.java:239)
      at
      hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:193)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:121)
      at hudson.model.Run.run(Run.java:559)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:132)
      at hudson.model.Executor.run(Executor.java:59)

        Attachments

          Activity

          Hide
          jasonchaffee Jason Chaffee added a comment -

          The workaround is to remove notifiers.

          Show
          jasonchaffee Jason Chaffee added a comment - The workaround is to remove notifiers.
          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          Fixed in 1.107.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - Fixed in 1.107.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jasonchaffee Jason Chaffee
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: