Hi Jim. Do you anticipate support across module boundaries given your comment?
282 // Navigating other modules via requires and exports is problematic 283 // since we cannot construct the runtime model of loaders and layers. it might be possible to emulate runtime resolution at link time for the set of idk.modules but not possible by default for non-idk modules because as you say we don’t know the runtime properties (such as layering), that would require some input from the developer (if it is indeed possible to express). I ask because there is a simpler way to express the current functionality, provide a method on ModuleEntry to obtain the LinkModule, rather than, or in addition to, the module name. Such functionality is much clearer regarding the scope of resolution. Paul. > On 8 Jul 2016, at 17:53, Jim Laskey (Oracle) <james.las...@oracle.com> wrote: > > http://cr.openjdk.java.net/~jlaskey/8161067/webrev/index.html > https://bugs.openjdk.java.net/browse/JDK-8161067 >
