Intended usage of `java --dry-run`?

[Peter Levart]

On 04/12/2017 04:22 PM, Alan Bateman wrote:
> On 11/04/2017 17:13, Andrew Guibert wrote:
>
>> :
>>
>> Thanks for clarifying Alan.  I misunderstood the use case of 
>> --dry-run to be
>> that it did not require any main class, but instead the point is to 
>> *load*
>> but not *execute* the main class.  Perhaps this would be worth 
>> clarifying in
>> the option description?
>>
>
> The current usage for this option does include "create VM but do not 
> execute main method". I guess we could adjust this a bit to make it 
> explicit that the main class is loaded but the main method is not 
> executed.
>
> -Alan

...and in addition, that the main class is not even initialized - no 
user code is executed, right? I think this excludes any java agents 
and/or custom system class loaders and/or custom security managers 
specified as command-line options. Perhaps this should be specified 
explicitly.

Regards, Peter