There are many classes using java.util.logging to log messages to enhance the diagnosability.  java.util.logging is a good candidate to be separated out as a module. We need to eliminate the dependency of logging from certain core classes for JDK modularization.

In addition to the dependency issue, Loggers are always created even if no log message is expected in the default configuration.

When a Logger is created, it triggers the logging initialization and set up based on the given configuration.  Most of the JRE log messages are of fine or lower level. It means that by default (level=INFO), no log message will be output which is desireable. However, the logging facility is still being initialized even though in the default case because it has no way to determine if it is the default configuration or not until it reads the JAVA_HOME/lib/logging.properties.

So this fix should help the startup performance (may not be significant though) as the logging facility is not initialized by default.