--dry-run description enhancement

David Holmes david.holmes at oracle.com
Tue Jul 12 06:46:53 UTC 2016

On 12/07/2016 4:00 PM, Paul Benedict wrote:
> Mandy, perhaps there is a JVM technicality here I'm unfamiliar with. My
> understanding of loading a class has always been that it's coupled with
> running its static initializers.

Loading, linking (resolution) and initialization are all distinct parts 
of making a Class available for use. Loading and linking can be eager or 
lazy, at the choice of the VM. initialization must only occur when 
specific interactions with the class are executed.


  So my inference was that the class does
> not get loaded into memory because the latter no longer occurs with
> --dry-run.
> On Jul 11, 2016 9:41 PM, "Mandy Chung" <mandy.chung at oracle.com> wrote:
>>> On Jul 12, 2016, at 10:35 AM, Paul Benedict <pbenedict at apache.org>
>> wrote:
>>> Mandy, can you please give a look to the first email in this thread and
>> see if you believe the enhanced message I suggested is helpful? I think it
>> would be.
>> Your Suggestion:
>> "create VM but do not load mainclass or execute main method”
>> The main class is loaded and your suggested text does not apply.  What
>> enhanced message do you refer to?
>> Mandy

More information about the core-libs-dev mailing list