Maven 2 & 3

NullPointerException, if MojoExecutionException has no message

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.7
  • Fix Version/s: 2.0.8
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

It seems, that you get a NPE, when a throwable passed to MojoExecutionExceptionDiagnoser.diagose(Throwable error) has no message, which means the message is null.

java.lang.NullPointerException
at org.apache.maven.usability.MojoExecutionExceptionDiagnoser.diagnose(MojoExecutionExceptionDiagnoser.java:64)
at org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(ErrorDiagnostics.java:84)
at org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:727)
at org.apache.maven.DefaultMaven.logError(DefaultMaven.java:672)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:131)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Line 64 --> if ( directCauseMessage != null && mee.getMessage().indexOf( directCauseMessage ) < 0 )
(Source: Revision 495147)

Issue Links

This issue is depended upon by:
MEXEC-29 exec:java throws NPE if the mainClass main method has not a correct signature Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graham Miller added a comment -

Could someone please post a workaround or fix for this soon. It's a showstopper, I can't tell why my build is broken, I only get the NPE. Thanks!

Show
Graham Miller added a comment - Could someone please post a workaround or fix for this soon. It's a showstopper, I can't tell why my build is broken, I only get the NPE. Thanks!
Hide
Permalink
Brian Fox added a comment - - edited

This was already fixed:

Revision: 576588
Author: carlos
Date: 5:18:01 PM, Monday, September 17, 2007
Message:
consider the case when exception message is null

Modified : /maven/components/branches/maven-2.0.x/maven-core/src/main/java/org/apache/maven/usability/MojoExecutionExceptionDiagnoser.java

I added unit tests to ensure it stays fixed, but MojoExecution and MojoFailure exceptions

Show
Brian Fox added a comment - - edited This was already fixed: Revision: 576588 Author: carlos Date: 5:18:01 PM, Monday, September 17, 2007 Message: consider the case when exception message is null
Modified : /maven/components/branches/maven-2.0.x/maven-core/src/main/java/org/apache/maven/usability/MojoExecutionExceptionDiagnoser.java I added unit tests to ensure it stays fixed, but MojoExecution and MojoFailure exceptions

People

Vote (6)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.