[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607504#comment-16607504
]
Rolf Schumacher commented on MCOMPILER-360:
-------------------------------------------
I can attach the project that caused the exception. It's absolutely free - at
least on my part. It's just a wrapper around Saxon that I've written years ago,
adapted to newer needs from time to time. I've loaded it to Eclipse Proton with
m2e. But it works in the same way if you just run "mvn test" from the command
line. I've set the JDK_JAVA_OPTIONS: --add-modules=java.se.ee.
In case this does not work for you (or even if it does), please provide me
instruction on how I can use your improved maven-compiler-plugin. I will report
the result.
> 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, xslt.zip
>
>
> 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)
