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

NPE during in parsing POMs for Multi Module Build

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • None
    • Debian Linux, Hudson 1.394, LANG=de_DE.UTF-8

      After update from 1.393 to 1394 to following NullPointerException appears in the log:

      Gestartet durch Benutzer hudson
      [patterntesting-check] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      [patterntesting-check-ct] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      [patterntesting-check-rt] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      [patterntesting-concurrent] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      ? hs_err_pid25523.log
      [patterntesting-exception] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      [patterntesting-libs] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      [patterntesting-rt] $ cvs -q -z3 update -PdC -D "Monday, January 17, 2011 10:54:47 AM UTC"
      $ no changes detected
      Found mavenVersion 2.2.1 from file jar:file:/usr/local/maven-2/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
      Parsing POMs
      ERROR: Processing failed due to a bug in the code. Please report this to hudson-users@googlegroups.com
      java.lang.NullPointerException
      at hudson.FilePath.isAbsolute(FilePath.java:224)
      at hudson.FilePath.<init>(FilePath.java:212)
      at hudson.FilePath.child(FilePath.java:894)
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:554)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
      at hudson.model.Run.run(Run.java:1362)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:145)
      project=hudson.maven.MavenModuleSet@7dab2e5f[10-patterntesting-libs-site]
      project.getModules()=[hudson.maven.MavenModule@69beea90[10-patterntesting-libs-site/org.patterntesting:patterntesting-check][10-patterntesting-libs-site/org.patterntesting:patterntesting-check][relativePath:null], hudson.maven.MavenModule@7519ca2c[10-patterntesting-libs-site/org.patterntesting:patterntesting-check-ct][10-patterntesting-libs-site/org.patterntesting:patterntesting-check-ct][relativePath:null], hudson.maven.MavenModule@70284ac3[10-patterntesting-libs-site/org.patterntesting:patterntesting-check-rt][10-patterntesting-libs-site/org.patterntesting:patterntesting-check-rt][relativePath:null], hudson.maven.MavenModule@654481bb[10-patterntesting-libs-site/org.patterntesting:patterntesting-concurrent][10-patterntesting-libs-site/org.patterntesting:patterntesting-concurrent][relativePath:null], hudson.maven.MavenModule@74a14fed[10-patterntesting-libs-site/org.patterntesting:patterntesting-exception][10-patterntesting-libs-site/org.patterntesting:patterntesting-exception][relativePath:null], hudson.maven.MavenModule@a868c6d[10-patterntesting-libs-site/org.patterntesting:patterntesting-libs][10-patterntesting-libs-site/org.patterntesting:patterntesting-libs][relativePath:], hudson.maven.MavenModule@76d4d81[10-patterntesting-libs-site/org.patterntesting:patterntesting-rt][10-patterntesting-libs-site/org.patterntesting:patterntesting-rt][relativePath:null]]
      project.getRootModule()=hudson.maven.MavenModule@a868c6d[10-patterntesting-libs-site/org.patterntesting:patterntesting-libs][10-patterntesting-libs-site/org.patterntesting:patterntesting-libs][relativePath:]
      FATAL: null
      java.lang.NullPointerException
      at hudson.FilePath.isAbsolute(FilePath.java:224)
      at hudson.FilePath.<init>(FilePath.java:212)
      at hudson.FilePath.child(FilePath.java:894)
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:554)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
      at hudson.model.Run.run(Run.java:1362)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:145)

      The same error messages appears if Maven-3 is used for this project.

          [JENKINS-8525] NPE during in parsing POMs for Multi Module Build

          ibruell added a comment -

          I have the same problem under Ubuntu 10.04 LTS with maven 2.2.1.

          ibruell added a comment - I have the same problem under Ubuntu 10.04 LTS with maven 2.2.1.

          jeremyt added a comment -

          I'm running on "x86_64 x86_64 x86_64 GNU/Linux CentOS release 5.2 (Final)"
          I am also running Maven 2.2.1 (installed automatically from Apache).

          I had pretty much the same error after upgrading Hudson to 1.394.
          Downgrading to Hudson 1.393 did NOT resolve the issue, however, downgrading Maven 2 Project Plugin from 1.394 to 1.393 DID make the problem go away.

          Hope this info is of some help.

          jeremyt added a comment - I'm running on "x86_64 x86_64 x86_64 GNU/Linux CentOS release 5.2 (Final)" I am also running Maven 2.2.1 (installed automatically from Apache). I had pretty much the same error after upgrading Hudson to 1.394. Downgrading to Hudson 1.393 did NOT resolve the issue, however, downgrading Maven 2 Project Plugin from 1.394 to 1.393 DID make the problem go away. Hope this info is of some help.

          oli_b added a comment - - edited

          yes, that helps (downgrading Maven 2 Project Plugin)

          Update (19-Jan-2011): Now (after downgrade) we have problems with another project which uses <packaging>oxt</packaging> from maven-ooo-plugin. Here we get the following error message:

          Parsing POMs
          ERROR: POMs konnten nicht geparst werden
          org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
          [ERROR] Unknown packaging: oxt @ line 25, column 14

          at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
          at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
          at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
          at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
          at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1103)
          at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:985)
          at hudson.FilePath.act(FilePath.java:756)
          at hudson.FilePath.act(FilePath.java:738)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:691)
          at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:527)
          at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
          at hudson.model.Run.run(Run.java:1362)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:401)
          at hudson.model.ResourceController.execute(ResourceController.java:88)
          at hudson.model.Executor.run(Executor.java:145)

          This error does not appear in 1.394

          oli_b added a comment - - edited yes, that helps (downgrading Maven 2 Project Plugin) Update (19-Jan-2011) : Now (after downgrade) we have problems with another project which uses <packaging>oxt</packaging> from maven-ooo-plugin. Here we get the following error message: Parsing POMs ERROR: POMs konnten nicht geparst werden org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] Unknown packaging: oxt @ line 25, column 14 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1103) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:985) at hudson.FilePath.act(FilePath.java:756) at hudson.FilePath.act(FilePath.java:738) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:691) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:527) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417) at hudson.model.Run.run(Run.java:1362) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:401) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:145) This error does not appear in 1.394

          Olivier Lamy added a comment -

          do you have any sample project to reproduce this ??

          Olivier Lamy added a comment - do you have any sample project to reproduce this ??

          oli_b added a comment -

          Hello Olivier,

          you can use PatternTesting which is accessible via CVS and where the config.xml is attached. If you use more infos let me know.

          regards,
          Oliver

          oli_b added a comment - Hello Olivier, you can use PatternTesting which is accessible via CVS and where the config.xml is attached. If you use more infos let me know. regards, Oliver

          Olivier Lamy added a comment -

          thanks !
          note for myself scm connection : :pserver:anonymous@patterntesting.cvs.sourceforge.net:/cvsroot/patterntesting

          Olivier Lamy added a comment - thanks ! note for myself scm connection : :pserver:anonymous@patterntesting.cvs.sourceforge.net:/cvsroot/patterntesting

          Olivier Lamy added a comment -

          Just testing with your config.xml and have the following issue

          [workspace] $ cvs -Q -z3 -d :pserver:anonymous@patterntesting.cvs.sourceforge.net:/cvsroot/patterntesting co -P -D "Wednesday, February 9, 2011 11:54:36 PM UTC" PatternTesting10/patterntesting-libs PatternTesting10/patterntesting-rt PatternTesting10/patterntesting-check PatternTesting10/patterntesting-check-ct PatternTesting10/patterntesting-check-rt PatternTesting10/patterntesting-concurrent PatternTesting10/patterntesting-exception
          cvs [checkout aborted]: connect to patterntesting.cvs.sourceforge.net(216.34.181.109):2401 failed: Connection refused
          FATAL: CVS failed. exit code=1
          Finished: FAILURE
          

          Olivier Lamy added a comment - Just testing with your config.xml and have the following issue [workspace] $ cvs -Q -z3 -d :pserver:anonymous@patterntesting.cvs.sourceforge.net:/cvsroot/patterntesting co -P -D "Wednesday, February 9, 2011 11:54:36 PM UTC" PatternTesting10/patterntesting-libs PatternTesting10/patterntesting-rt PatternTesting10/patterntesting-check PatternTesting10/patterntesting-check-ct PatternTesting10/patterntesting-check-rt PatternTesting10/patterntesting-concurrent PatternTesting10/patterntesting-exception cvs [checkout aborted]: connect to patterntesting.cvs.sourceforge.net(216.34.181.109):2401 failed: Connection refused FATAL: CVS failed. exit code=1 Finished: FAILURE

          oli_b added a comment -

          At the moment CVS is not working at Sourceforge, see http://sourceforge.net/apps/trac/sourceforge/ticket/17197

          oli_b added a comment - At the moment CVS is not working at Sourceforge, see http://sourceforge.net/apps/trac/sourceforge/ticket/17197

          oli_b added a comment -

          oli_b added a comment - CVS is back again, see http://sourceforge.net/blog/update-on-scm-services/

          Marco Rothe added a comment - - edited

          Seams to be the same problem as http://issues.jenkins-ci.org/browse/JENKINS-8602. Maybe introduced by the refactoring of the toPomInfo method because of the maven3 stuff

          Marco Rothe added a comment - - edited Seams to be the same problem as http://issues.jenkins-ci.org/browse/JENKINS-8602 . Maybe introduced by the refactoring of the toPomInfo method because of the maven3 stuff

          ibruell added a comment -

          I upgraded to jenkins 1.397 and the problem still exists.

          ibruell added a comment - I upgraded to jenkins 1.397 and the problem still exists.

          Code changed in jenkins
          User: Olivier Lamy
          Path:
          maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
          http://jenkins-ci.org/commit/core/be09ca67a6237cd176dd9e8562ae86adb85a38f0
          Log:
          [FIXED JENKINS-8525] NPE during in parsing POMs for Multi Module Build

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Olivier Lamy Path: maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/core/be09ca67a6237cd176dd9e8562ae86adb85a38f0 Log: [FIXED JENKINS-8525] NPE during in parsing POMs for Multi Module Build

          Code changed in jenkins
          User: Olivier Lamy
          Path:
          changelog.html
          http://jenkins-ci.org/commit/core/14161627eacfaea2f994411d073b9ec32ab96d47
          Log:
          changelog for JENKINS-8525

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Olivier Lamy Path: changelog.html http://jenkins-ci.org/commit/core/14161627eacfaea2f994411d073b9ec32ab96d47 Log: changelog for JENKINS-8525

          dogfood added a comment -

          Integrated in jenkins_main_trunk #525
          [FIXED JENKINS-8525] NPE during in parsing POMs for Multi Module Build
          changelog for JENKINS-8525

          Olivier Lamy :
          Files :

          • maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java

          Olivier Lamy :
          Files :

          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #525 [FIXED JENKINS-8525] NPE during in parsing POMs for Multi Module Build changelog for JENKINS-8525 Olivier Lamy : Files : maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java Olivier Lamy : Files : changelog.html

          Marco Rothe added a comment -

          Works for me now (build starts with sucess with 1.400-SNAPSHOT), but some of the related bugs are still open.

          Marco Rothe added a comment - Works for me now (build starts with sucess with 1.400-SNAPSHOT), but some of the related bugs are still open.

          ndg added a comment -

          Still occurs in version 1.399 -> please release this in next version...

          ndg added a comment - Still occurs in version 1.399 -> please release this in next version...

          Marco Rothe added a comment -

          The patch (see JENKINS-7684) was applied to the master 1.400-SNAPSHOT => so with the release of 1.400 it will become "public"

          Marco Rothe added a comment - The patch (see JENKINS-7684 ) was applied to the master 1.400-SNAPSHOT => so with the release of 1.400 it will become "public"

          ndg added a comment -

          Ok. I was just looking when this would occur as I did not see a Fix Version nor a roadmap version v1.400 with a due date.

          Thnx for the efforts!

          ndg added a comment - Ok. I was just looking when this would occur as I did not see a Fix Version nor a roadmap version v1.400 with a due date. Thnx for the efforts!

          Code changed in jenkins
          User: Olivier Lamy
          Path:
          src/main/java/hudson/maven/MavenModuleSetBuild.java
          http://jenkins-ci.org/commit/maven-plugin/337b8729636310ff725964025f9cbda7583dfa81
          Log:
          [FIXED JENKINS-8525] NPE during in parsing POMs for Multi Module Build

          Originally-Committed-As: be09ca67a6237cd176dd9e8562ae86adb85a38f0

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Olivier Lamy Path: src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/maven-plugin/337b8729636310ff725964025f9cbda7583dfa81 Log: [FIXED JENKINS-8525] NPE during in parsing POMs for Multi Module Build Originally-Committed-As: be09ca67a6237cd176dd9e8562ae86adb85a38f0

            olamy Olivier Lamy
            oli_b oli_b
            Votes:
            13 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: