Page Comparison

...

There's no straightforward way to silence these warnings. The JVM command line parameter that controls it is --illegal-access=<policy> (see https://docs.oracle.com/en/java/javase/11/tools/java.html), it is set to permit by default — warning on first illegal access only per library and class — and that is the most liberal option. We can use --add-opens though. It can entirely open one module — export all its classes —  to another. The illegal accesses here

Jira Legacy
server System JIRA serverId 50130123-f232-3df4-bccb-c16e7d83cd3e key CORE-1438

are to internal JDK APIs. We could therefore then open JDK to problematic modules. Most, if not all, of library libraries we use don't support modularity and I'm not sure how the new JVM treats old world where there's just bunch of JARs on CLASSPATH. There was some proposal on Automatic Modules that would turn JARs into modules, but I'm not sure how the development has evolved.

For details see

• https://en.wikipedia.org/wiki/Java_Platform_Module_System
• https://openjdk.java.net/projects/jigsaw/spec/sotms/
• https://openjdk.java.net/projects/jigsaw/
• https://mreinhold.org/blog/jigsaw-complete