- 
    
Bug
 - 
    Resolution: Unresolved
 - 
    
Major
 - 
    RedHat Linux, Java 1.6.0_26.
 
Just updated to Jenkins 1.445 from 1.427 and now am getting this NPE; looks like either the MojoDescriptor or PluginDescriptor param to getMojoClass() is null, or else classRealm (in the latter case, might have been fixed by olamy's changes on Dec 29th):
Caused by: java.lang.NullPointerException
	at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
	at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
	at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
	at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
	at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
Last message logged prior to this seems to be:
[DEBUG] Looking up lifecyle mappings for packaging pom from ClassRealm[plexus.core, parent: null]
This is in a child project, not the parent.
- is duplicated by
 - 
                    
JENKINS-12269 Latest build 1.445 breaks regression in Maven
-         
 - Resolved
 
 -         
 - 
                    
JENKINS-12358 NullPointerException when Maven project is configured to generate Javadoc
-         
 - Resolved
 
 -