I have asked for a mechanism to avoid the warnings multiple times and there is no way to do it.
That's unfortunate because there are multiple projects that have been modified to work with JDK9 and they still produce a warning. I have resorted to keeping a list of known warnings that are OK (currently at 10). Here are a few public (non-Oracle) ones: org.python.core.PyJavaClass com.sun.xml.bind.v2.runtime.reflect.opt.Injector com.sun.xml.ws.model.Injector net.sf.cglib.core.ReflectUtils$ -----Original Message----- From: Jochen Theodorou [mailto:blackd...@gmx.org] Sent: Sunday, July 9, 2017 7:17 PM To: jigsaw-dev@openjdk.java.net Subject: trySetAccessible Hi all, since the JVM now prints warnings if you call setAccssible there was the advise to move to trySetAccessible to prvent these warnings. Now I am told those warnings appear here as well. Now my question would be about what the intended behaviour here is. in what mode is a trySetAccessible supposed to cause the JVM to issue a warning or other message about a module accessing something? And if the warnings are the intended behaviour, then what is the way to avoid this if I cannot just stop trying? bye Jochen
