[jsr294-modularity-eg] 294 EG conf call, 2009-04-08

Bryan Atsatt bryan.atsatt at oracle.com
Mon Apr 13 20:18:57 EDT 2009


In the ModulePath idea from [2], the module name (and an optional 
version) are encoded as a directory name, which is assumed to be a child 
of a -modulepath directory reference. From page 10:

    src/modules/com.foo.app/com/foo/HelloWorld.java
                           /module-info.java
               /com.bar.app/com/bar/Baz.java
                           /module-info.java

where "src/modules" is the -modulepath reference (apologies if the 
formatting didn't make it through ;^).

Are you assuming that the child directory name is required to match the 
name (and version) declared within the enclosed module-info.java file? 
Or would this simply be a useful convention?

IOW, is there some lookup logic assumed here, allowing the compiler to 
search for the module-info for "com.bar.app" without cracking open the 
module-info files?

// Bryan
> [1]http://mail.openjdk.java.net/pipermail/jigsaw-dev/2009-April/000076.html 
>
> [2]http://openjdk.java.net/projects/jigsaw/doc/ModulesAndJavac.pdf
>
> _______________________________________________
> jsr294-modularity-eg mailing list
> jsr294-modularity-eg at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/jsr294-modularity-eg/attachments/20090413/e6865152/attachment.html>


More information about the jsr294-modularity-eg mailing list