[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608451#comment-16608451
]
Robert Scholte commented on MCOMPILER-360:
------------------------------------------
That test does indeed require a {{toolchains.xml}} file on your sytem.
To only run this test, try to add {{-Dinvoker.test=MCOMPILER-360*}}
> nullpointer exception
> ---------------------
>
> Key: MCOMPILER-360
> URL: https://issues.apache.org/jira/browse/MCOMPILER-360
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.8.0
> Environment: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4
> (2018-08-21) x86_64 GNU/Linux
> java version "10.0.2" 2018-07-17
> Apache Maven 3.5.4
> Reporter: Rolf Schumacher
> Priority: Major
> Labels: build, maven, newbie
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt
>
>
> Trying to migrate an saxon/fop maven project to Java 10.
> Added module-info.java, entered all required Automatic names. No compiler
> failures in Eclipse. Running "mvn -e test" leads to 2 warnings and a
> maven-compile-plugin error
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> (default-compile) on project xslt: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed.
> NullPointerException -> [Help 1]
> Full output is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
