[11] RFR JDK-8191170: Clarify if java.class.path can be undefined

Alan Bateman Alan.Bateman at oracle.com
Wed Jan 24 18:25:48 UTC 2018



On 24/01/2018 18:02, mandy chung wrote:
> :
>
> Thanks for the suggestion.  Updated version:
>
>      * <p> The name of the built-in system class loader is {@code "app"}.
>      * The system property "{@code java.class.path}" is read during early
>      * initialization of the VM to determine the class path.
>      * An empty value of "{@code java.class.path}" property is interpreted
>      * differently depending on whether the initial module (the module
>      * containing the main class) is named or unnamed:
>      * If named, the built-in system class loader will have no class 
> path and
>      * will search for classes and resources using the application 
> module path;
>      * otherwise, if unnamed, it will set the class path to the current
>      * working directory.
This looks good.

-Alan


More information about the core-libs-dev mailing list