Java Platform Module System
Alan Bateman
Alan.Bateman at oracle.com
Tue Jun 6 09:03:15 UTC 2017
On 06/06/2017 09:40, Stephan Herrmann wrote:
>
> This was viewed from the JLS p.o.v. But "read by M" is still not
> well-defined.
> All we see in the documentation of the referenced method is:
>
> "a readability graph is computed"
>
> With some further searching, we find "readability graph" explained in the
> toplevel documentation of class Configuration.
>
> But where in the specification (combination of JLS and API doc) should we
> learn the connection between "read" and "requires"? As far as I can see
> this fundamental connection is totally implicit.
>
> I know what is meant, but for the final specification this is still needs
> to be improved. The specification shouldn't expect the reader to already
> know what is specified prior to reading :)
>
> Additionally, this missing link in the specification hides the fact
> that it is unspecified how "transitive" contributes to "reads",
> which is more severe than the editorial aspect of it.
Resolution is specified in the java.lang.module package description
(remember this package description was re-worked to address
#ResolutionAtCompileTime [1]). In the JSR's working draft specification,
you can find it here:
http://cr.openjdk.java.net/~mr/jigsaw/spec/api/java/lang/module/package-summary.html
It's identical to the javadoc that is published with the Jigsaw EA builds.
-Alan.
[1]
http://openjdk.java.net/projects/jigsaw/spec/issues/#ResolutionAtCompileTime
More information about the jigsaw-dev
mailing list