Posted by douglaslyon on Jan 03, 2018; 11:20pm
URL: https://forum.jogamp.org/Jogl-Jogamp-on-Java-9-tp4038012p4038481.html

Hi Julien,
It is quite possible that I have the --add-opens incorrectly
formatted... This is what I have, so far:

  <resources>
     <j2se version="1.8+"
     initial-heap-size="64m"
     max-heap-size="384m"
     java-vm-args="-ea --add-opens=java.base/java.util=ALL-UNNAMED"
     />

     <extension name="Java3D"  href="jogl.jnlp">
     </extension>
     <jar href="joglquad.jar" />
   </resources>

I am very unsure about --add-opens=java.base/java.util=ALL-UNNAMED
perhaps --add-opens java.base/=ALL-UNNAMED ?
Not sure about that at all...really.

Any ideas?

Should I be using add-exports?
http://openjdk.java.net/jeps/261 says:

"It is sometimes necessary to violate the access-control boundaries
defined by the module system, and enforced by the compiler and virtual
machine, in order to allow one module to access some of the unexported
types of another module. This may be desirable in order to, e.g., enable
white-box testing of internal types, or to expose unsupported internal
APIs to code that has come to depend upon them. The --add-exports option
can be used, at both compile time and run time, to do this. Its syntax is:

--add-exports <source-module>/<package>=<target-module>(,<target-module>)*"

The --add-exports option enables access to the public types of a
specified package. It is sometimes necessary to go further and enable
access to all non-public elements via the setAccessible method of the
core reflection API. The --add-opens option can be used, at run time, to
do this. It has the same syntax as the --add-exports option:

--add-opens <source-module>/<package>=<target-module>(,<target-module>)*

where <source-module> and <target-module> are module names and <package>
is the name of a package.

--- I must say, both extensions are all very new, to me.

Thanks!
  - Doug



On 1/3/18 2:46 PM, gouessej [via jogamp] wrote: