2017-09-05 22:16 GMT+09:00 Alan Bateman :
> The issue here is that org.astro is not resolved because no module requires
> org.astro. If you add `--add-modules org.astro` to the command line then it
> will ensure that this module is resolved and you should see that
> com.greetings reads it.
Thank y
On 05/09/2017 14:08, KUBOTA Yuji wrote:
My following example program shows that automatic module can't read
exported package by explicit module.
$ /jdk-9/bin/jar -d --file mlibs/org.astro.jar
org.astro jar:file:///jigsaw-sample/mlibs/org.astro.jar/!module-info.class
exports org.astro
requires
Hi Alan,
Thank you very much for your quickly and detailed explanation!
I think that your explanation make sense except accessibility of automatic
module.
My following example program shows that automatic module can't read
exported package by explicit module.
$ /jdk-9/bin/jar -d --file mlibs/org
On 05/09/2017 12:01, KUBOTA Yuji wrote:
Hi all,
I have a question about accessibility of each modules: unnamed,
automatic and named modules.
* unnamed: the JAR compiled by java 8 and speficied by --class-path.
* automatic: the JAR compiled by Java 8 and specified by --module-path.
* named: the m
Hi all,
I have a question about accessibility of each modules: unnamed,
automatic and named modules.
* unnamed: the JAR compiled by java 8 and speficied by --class-path.
* automatic: the JAR compiled by Java 8 and specified by --module-path.
* named: the modular JAR.
I ran quick-start's example p
