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

[Paul Sandoz]

> On Jan 24, 2018, at 3:36 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> 
> On 23/01/2018 22:40, mandy chung wrote:
>> http://cr.openjdk.java.net/~mchung/jdk11/webrevs/8191170/webrev.00/index.html 
>> 
>> A small adjustment in the javadoc.  It clarifies what an empty value of "java.class.path" property is interpreted by the built-in application class loader.
> It looks okay but I had to read it a few times.

Same here.


> 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;"

Paul.