[11] RFR JDK-8191170: Clarify if java.class.path can be undefined (original) (raw)
mandy chung mandy.chung at oracle.com
Wed Jan 24 18:02:28 UTC 2018
- Previous message: [11] RFR JDK-8191170: Clarify if java.class.path can be undefined
- Next message: [11] RFR JDK-8191170: Clarify if java.class.path can be undefined
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/24/18 8:48 AM, Paul Sandoz wrote:
A few suggestions that might make it a bit easier to read:
"It reads the system property java.class.path ..." => "The system property java.class.path is read ..." "is named or not" => "is named or unnamed". "whether the initial module" => "whether the initial module (the module containing the main class)”. +1 to those. That sufficiently explains the initial module. "If named, the built-in system class loader will have no class path i.e. only find classes and resources only from the application module path;” => “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;"
Thanks for the suggestion. Updated version:
*
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.
Mandy
- Previous message: [11] RFR JDK-8191170: Clarify if java.class.path can be undefined
- Next message: [11] RFR JDK-8191170: Clarify if java.class.path can be undefined
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]