Hi Alan,
+ * If neither of these properties is defined then the LogManager uses its
+ * default configuration. The default configuration is typically loaded from
the
+ * properties file "{@code lib/logging.properties}" in the Java installation
+ * directory.
Will typical become atypical for OpenJDK by the time Java 9 ships?
Paul.
On Nov 25, 2012, at 11:07 PM, Alan Bateman <alan.bate...@oracle.com> wrote:
>
> As part of preparing for modules [1], we need to examine a number of
> normative references to files in ${java.home} with a view to downgrading
> these references to non-normative status. This is important as we need the
> flexibility to eventually move some of these files into module-private
> locations, maybe in some cases replace them with something else. This is
> something I've bought up on security-dev and i18n-dev recently as there are
> number of references to files in ${java.home} that need to be examined.
>
> The focus of this mail is java.util.logging.LogManager as it specifies that
> the default configuration is loaded from ${java.home}/lib/logging.properties.
> Clearly this file is changed in some environments, although running with
> java.util.logging.config.file is probably more robust in that the settings
> can be used with different JDK installations. The proposed changes (javadoc
> changes only, no implementation changes) is here:
> http://cr.openjdk.java.net/~alanb/8003949/webrev/
>
> Note that I have also removed the statement that "properties may be set via
> the Preference API" as the implementation has never used the preferences and
> not worth re-visiting now.
>
> -Alan
>
> [1] http://openjdk.java.net/jeps/162
