On 7.11.2015 15:34, Alan Bateman wrote:
On 07/11/2015 10:15, Florian Troßbach wrote:
:
When I compile my modules with
javac -d . -mp ../jars -modulesourcepath . -verbose $(find . -name
"*.java")
I get the attached output. The raised error is "error: cannot find
module:
jdk.management.resource”.
This is a bug in the EA build where they are qualified exports to
jdk.management.resource but this module is not in the builds. So it's a
build issue, I'll create a bug to track this. If you build the JDK
yourself, from the jigsaw/jake sources, then you won't run into this
issue, it is specified to how the EA builds are created.
That said, I'm not 100% sure why javac runs into it here, I'm sure Jon
or Jan can explain that.
Automatic modules depend on all other named modules, and javac currently
uses all modules it knows about, which includes those it found while
analyzing other module-infos. I think it could be changed to only
include modules found on the module paths.
Jan
-Alan.
