> On Nov 28, 2017, at 2:35 AM, Alan Bateman <alan.bate...@oracle.com> wrote: > > One point that I didn't see mentioned in the thread so far is a detail in the > JEP 261 policy on root modules for the case that module java.se > <http://java.se/> is not observable. When java.se <http://java.se/> is not > observable then all modules (system or upgrade module path) that export an > API are resolved. The output of `java --list-modules` will answer his quickly > but I'll bet the image doesn't have java.se <http://java.se/>.
I added this. It works. java.corba included and the scheduler still working. Still looking forward to the changes of course but this seems to give something to go on. Thanks again. HalfPipe7.app/Contents/PlugIns/Java.runtime/Contents/Home/bin/java --list-modules java.activation@9 java.base@9 java.compiler@9 java.corba@9 java.datatransfer@9 java.desktop@9 java.instrument@9 java.logging@9 java.management@9 java.management.rmi@9 java.naming@9 java.prefs@9 java.rmi@9 java.scripting@9 java.se@9 java.security.jgss@9 java.security.sasl@9 java.sql@9 java.sql.rowset@9 java.transaction@9 java.xml@9 java.xml.bind@9 java.xml.crypto@9 jdk.attach@9 jdk.compiler@9 jdk.internal.ed@9 jdk.internal.jvmstat@9 jdk.internal.le@9 jdk.internal.opt@9 jdk.jdi@9 jdk.jdwp.agent@9 jdk.jshell@9 jdk.unsupported@9
