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
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
> From: Alan Bateman <alan.bate...@oracle.com>
> To: Andrew Guibert/Rochester/IBM@IBMUS, jigsaw-dev d...@openjdk.java.net>
> Date: 04/11/2017 10:00 AM
> Subject: Re: Intended usage of `java --dry-run`?
>
> On 11/04/2017 15:36, Andrew Guibert wrote:
>
> > :
&g
On 11/04/2017 15:36, Andrew Guibert wrote:
:
Based on these three use cases, either I'm using --dry-run incorrectly
(which isn't obvious if I am) or --dry-run is simply a placebo option. My
main point of confusion comes from (what I believe to be) correct usage of
--dry-run printing out usage
I'm working with JDK build b162 and I see that the following option is
listed:
--dry-run create VM but do not execute main method.
This --dry-run option may be useful for validating the
command-line options such as the module system
configuration.
