[ 
https://issues.apache.org/jira/browse/MCOMPILER-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998447#comment-16998447
 ] 

Jörg Hohwiller commented on MCOMPILER-359:
------------------------------------------

[https://api.travis-ci.org/v3/job/626312654/log.txt]

Caused by: java.lang.NullPointerException at 
org.apache.maven.plugin.compiler.TestCompilerMojo.preparePaths 
(TestCompilerMojo.java:254) at 
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute 
(AbstractCompilerMojo.java:792)

[https://github.com/apache/maven-compiler-plugin/blob/master/src/main/java/org/apache/maven/plugin/compiler/TestCompilerMojo.java#L254]

I assume line number does not exactly fit here. But as already guessed 
Throwable cause may already be null. So this is just unsafe code that needs to 
be fixed.

PR:

https://github.com/apache/maven-compiler-plugin/pull/28

> plexus-java 0.9.10 causes a NullPointer in compiler-plugin 3.8.0
> ----------------------------------------------------------------
>
>                 Key: MCOMPILER-359
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-359
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.8.0
>         Environment: Windows 7
> JDK 10.0.2
> Maven 3.5.4
>            Reporter: Marvin
>            Priority: Major
>         Attachments: plugintest.zip
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If {{<dependencies>}} contains a {{<type>pom</type>}} or {{<type>war</type>}} 
> this call:
>      {{moduleDescriptor = binaryParser.getModuleDescriptor( path );}}
>  throws an {{IOException}}:
>      {{zip END header not found}}
>  because the file is being treated as a jar file.
>  When the call returns to {{CompilerMojo.preparePaths()}} this call returns 
> {{null}}:
>      {{Throwable cause = pathException.getValue().getCause();}}
>  and the next line throws a {{NullPointerException}}:
>      {{while ( cause.getCause() != null )}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to