maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MNG-3077) NullPointerException, if MojoExecutionException has no message
Date Sat, 05 Jan 2008 03:34:57 GMT

    [ http://jira.codehaus.org/browse/MNG-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110130
] 

brianfox edited comment on MNG-3077 at 1/4/08 9:33 PM:
--------------------------------------------------------

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

      was (Author: brianfox):
    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 unsure it stays fixed, but MojoExecution and MojoFailure exceptions
  
> NullPointerException, if MojoExecutionException has no message
> --------------------------------------------------------------
>
>                 Key: MNG-3077
>                 URL: http://jira.codehaus.org/browse/MNG-3077
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.7
>            Reporter: Johannes Konstantinidis
>            Assignee: Brian Fox
>             Fix For: 2.0.8
>
>
> 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)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message