On Thu, Apr 9, 2020 at 7:37 PM Alan Bateman <alan.bate...@oracle.com> wrote:
The only packaging format for automatic modules that Java SE defines is > JAR files. The "Multi-release JAR files" feature is also JAR file only. > My ModuleFinder for exploded-within-jar automatic modules needed a ModuleReader implementation. I decided to make that ModuleReader multi-release-aware. Like JarFile, it inspects the manifest for the Multi-Release attribute and scans META-INF/version directories accordingly. Is it safe to assume that all access to content with a module happens through the ModuleReader? Eirik.
