I've just upgraded to 109 (but not trunk) and reproduced it:
1. I created a new job.
2. I used the Copy feature to copy an existing one (I'm trying to break a large
build into smaller sub-modules).
3. I edited the remote svnroot to the new location (sub-directory) and changed
the root pom to 'pom.xml'.
4. Saved.
At this point, Hudson tried to check out everything from the old svn location. I
did "Reload Configuration from Disk" (even though I hadn't edited anything
manually) and started the build again and this time it got it from the right place.
After checking it all out and listing the maven sub-modules correctly, the
console output page showed this error:
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.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:230)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:127)
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.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:230)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:127)
at hudson.model.Run.run(Run.java:559)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:132)
at hudson.model.Executor.run(Executor.java:59)
The config.xml has:
<rootModule>
<groupId>org.gria</groupId>
<artifactId>base</artifactId>
</rootModule>
This is the root of the job I copied, not the new one.
I think I fixed this in 1.110, but it's not obvious to me why the scenario you
explained to me would cause your problem.
If you could check the latest snapshot, that would be great. Or if you have the
complete stack trace of NPE, that would be also very helpful.