> On 5 May 2017, at 02:32, Chris Hegarty <chris.hega...@oracle.com> wrote: > > >> On 4 May 2017, at 22:14, Paul Sandoz <paul.san...@oracle.com> wrote: >> >> New update here: >> >> http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8150681-jar-spec-markdown-with-mr-jar/webrev/src/java.base/share/specs/jar/jar.md.sdiff.html >> >> <http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8150681-jar-spec-markdown-with-mr-jar/webrev/src/java.base/share/specs/jar/jar.md.sdiff.html> > > I read through the changes for modular and multi-release JAR, > they seem fine. > >> I accepted most comments directly. I shuffled around the paragraphs in the >> modular jar section, partially in preparation for any changes and further >> explanations for automatic modules. > > I know you may have further changes here resulting from ongoing > discussion around automatic modules, but I think the following could > be resolved now. > > "If a multi-release JAR file is deployed on the class path of major version …" > > The MR JAR can also be put on module path, it is not exclusive to the > class path, or limited to only Modular multi-release JARs on the module path. >
Ok, i can refine to say: If a multi-release JAR file is deployed on the class path or module path (as an automatic module or an explicit [multi-release module](#Modular-multi-release)) and i can remove the paragraph in the Modular-multi-release in class loading. Paul.
