• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • maven-plugin
    • None
    • Platform: Sun, OS: Solaris

      I add a new module in my m2 reactor build and I have the following stack trace :

      Parsing POMs
      ERROR: Processing failed due to a bug in the code. Please report this to
      users@hudson.dev.java.net
      java.lang.NullPointerException
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:430)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:354)
      at hudson.model.Run.run(Run.java:1120)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:123)
      project=hudson.maven.MavenModuleSet@1f95cce[accommons-libs]
      project.getModules()=[hudson.maven.MavenModule@1f2412a[accommons-libs/com.accor.commons:accommons-libs-root],
      hudson.maven.MavenModule@194566d[accommons-libs/com.accor.commons:split-tars],
      hudson.maven.MavenModule@1b64b70[accommons-libs/com.accor.commons.cache:accommons-cache],
      hudson.maven.MavenModule@112bc7b[accommons-libs/com.accor.commons.configuration:plexus-configuration],
      hudson.maven.MavenModule@11456c5[accommons-libs/com.accor.commons.configuration:plexus-configuration-api],
      hudson.maven.MavenModule@4ca42b[accommons-libs/com.accor.commons.configuration:plexus-configuration-jdbc],
      hudson.maven.MavenModule@1ae0e7d[accommons-libs/com.accor.commons.configuration:plexus-configuration-prefs],
      hudson.maven.MavenModule@393167[accommons-libs/com.accor.commons.plexus:accommons-plexus-utils],
      hudson.maven.MavenModule@da8742[accommons-libs/com.accor.commons.plexus.components:accommons-plexus-components],
      hudson.maven.MavenModule@e637f0[accommons-libs/com.accor.commons.plexus.components:jdbc-connection-pool],
      hudson.maven.MavenModule@627b5c[accommons-libs/com.accor.commons.plexus.components:stored-procedure-parser],
      hudson.maven.MavenModule@190d536[accommons-libs/com.accor.commons.prefs:accommons-prefs],
      hudson.maven.MavenModule@19deddb[accommons-libs/com.accor.commons.storedprocedure:stored-procedure-executor],
      hudson.maven.MavenModule@16acad2[accommons-libs/com.accor.commons.storedprocedure:stored-procedure-executor-api],
      hudson.maven.MavenModule@29b849[accommons-libs/com.accor.commons.storedprocedure:stored-procedure-executor-model],
      hudson.maven.MavenModule@101e081[accommons-libs/com.accor.commons.tools:accommons-tools],
      hudson.maven.MavenModule@157f72[accommons-libs/com.accor.commons.tools:jersey-apache-client],
      hudson.maven.MavenModule@3a4822[accommons-libs/com.accor.commons.transporter:file-transporters],
      hudson.maven.MavenModule@55bfaf[accommons-libs/com.accor.commons.xmlschemas:schemas-validator],
      hudson.maven.MavenModule@19b7c62[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-api],
      hudson.maven.MavenModule@1031310[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-jaxp],
      hudson.maven.MavenModule@d8978c[accommons-libs/com.accor.commons.xmlschemas:schemas-validator-msv],
      hudson.maven.MavenModule@1c5a33b[accommons-libs/com.accor.components.cache:spring-cache],
      hudson.maven.MavenModule@5facbd[accommons-libs/com.accor.components.cache:spring-cache-api],
      hudson.maven.MavenModule@145c414[accommons-libs/com.accor.components.cache:spring-cache-ehcache],
      hudson.maven.MavenModule@14c02d4[accommons-libs/com.accor.components.cache:spring-cache-hashmap],
      hudson.maven.MavenModule@14db52b[accommons-libs/com.accor.components.cache:spring-cache-oscache],
      hudson.maven.MavenModule@b124fa[accommons-libs/com.accor.components.cache:spring-cache-providers],
      hudson.maven.MavenModule@1f2a9da[accommons-libs/com.accor.components.cache:spring-cache-test],
      hudson.maven.MavenModule@6d4f30[accommons-libs/com.accor.components.cache:spring-cache-whirlycache],
      hudson.maven.MavenModule@6a150e[accommons-libs/com.accor.hudson.plugins:hudson-plugins],
      hudson.maven.MavenModule@8c4b5f[accommons-libs/com.accor.hudson.plugins:mavenrelease],
      hudson.maven.MavenModule@a84b47[accommons-libs/commons-logging:commons-logging],
      hudson.maven.MavenModule@e64795[accommons-libs/commons-logging:commons-logging-api],
      hudson.maven.MavenModule@659812[accommons-libs/commons-logging:commons-logging-parent]]
      project.getRootModule()=hudson.maven.MavenModule@1f2412a[accommons-libs/com.accor.commons:accommons-libs-root]
      FATAL: null
      java.lang.NullPointerException
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:430)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:354)
      at hudson.model.Run.run(Run.java:1120)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:303)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:123)

          [JENKINS-4624] NPE when adding a new module in reactors.

          Olivier Lamy added a comment -

          so it looks to happen only with " Incremental build " feature enabled.

          Olivier Lamy added a comment - so it looks to happen only with " Incremental build " feature enabled.

          Andrew Bayer added a comment -

          Ah-ha - I think I know what's causing this now. The incremental build logic is
          choking when faced with a new module - for right now, I'd suggest you run a
          build without the incremental build functionality enabled, and then re-enable
          the incremental build option afterwards, to make sure the new module is
          registered properly. I'll fix the underlying issue later today.

          Andrew Bayer added a comment - Ah-ha - I think I know what's causing this now. The incremental build logic is choking when faced with a new module - for right now, I'd suggest you run a build without the incremental build functionality enabled, and then re-enable the incremental build option afterwards, to make sure the new module is registered properly. I'll fix the underlying issue later today.

          Code changed in hudson
          User: : abayer
          Path:
          trunk/hudson/main/maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
          trunk/hudson/main/test/src/test/java/hudson/maven/MavenMultiModuleTest.java
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=22535
          Log:
          [FIXED JENKINS-4624] Fixed in 1.329 - checks to be sure there's been a previous build before we try to get the changeset for a module

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : abayer Path: trunk/hudson/main/maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java trunk/hudson/main/test/src/test/java/hudson/maven/MavenMultiModuleTest.java trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=22535 Log: [FIXED JENKINS-4624] Fixed in 1.329 - checks to be sure there's been a previous build before we try to get the changeset for a module

            abayer Andrew Bayer
            olamy Olivier Lamy
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: