when issue https://bugs.openjdk.java.net/browse/JDK-8136802 happens, we got a error message "java.lang.InternalError: legacy getBundle can't be used to find test.pkg.ClassResource in module mod.test". but maybe it's better to throw MissingResourceBundleException.

Below is from Daniel :
if some code in an unnamed module calls ResourceBundle.getBundle,
passing (maybe by mistake) the name of a resource bundle that happens
to be located in a named module, then in my opinion it should get
MissingResourceBundleException, not InternalError.

This is fine for prototyping and debugging - but I hope InternalError
will be replaced in the final implementation.