[
https://issues.apache.org/jira/browse/MCOMPILER-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651899#comment-16651899
]
Jezza commented on MCOMPILER-360:
---------------------------------
I built a local snapshot (3.8.1-SNAPSHOT), and it works.
Just waiting for a release to "officially" use it.
I don't think it's a perfect solution, as I get warnings like:
{noformat}
[WARNING] Can't extract module name from jaxws-ri-2.3.1.pom: zip END header not
found
[WARNING] Can't extract module name from jaxb-ri-2.4.0-b180830.0438.pom: zip
END header not found
{noformat}
Ideally, they should automatically dumped on the classpath instead of failing
to be read.
Other than that, it works.
> NPE when calculating modulepath with invalid entries
> ----------------------------------------------------
>
> 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
> Assignee: Robert Scholte
> Priority: Major
> Labels: build, maven, newbie
> Fix For: 3.8.1
>
> Attachments: 2018-09-06-stacktrace.txt, MCOMPILER-360.tar.gz,
> mvn-verify-result.txt, with-Dinvoker.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)