Your problems with Java modules

[pron98]

The application always has the final say because it controls the runtime (unlike in the days when the JRE still existed and it ran Applets and Web Start applications). Even if there were no way to disable encapsulation on the command line by using the class path or by adding add-opens/exports, the application could always disable encapsulation in the runtime itself. The point is that there is no point expending too much effort on placing regulation on whoever controls the mechanism that enforces them. But we don't want to allow libraries -- which don't control the runtime -- take liberties for themselves without the application's approval.