>> Okay. On the the ZipFileSystem then it would be good to get a summary on >> what you are proposing. > > Details of any JavacFileManager/ZipFileSystem support are still being hashed > out. They are mentioned in the JEP and we can update once those details are > finalized.
To elaborate a bit, the implementation is quite straight forward. ZipFileSystem builds an Inode tree on open. That tree is implemented as a Map<Inode,Inode>. For regular zip/jar files both the key and the value are the same Inode. For multi-release jar files the value is the Inode of the appropriate versioned entry. Configuration is through the Map<String,?> env parameter to the FileSystems.newFileSystem parameter.
