Hi Paul,
On 7/12/16 8:00 AM, 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. So my inference was that the class does
not get loaded into memory because the latter no longer occurs with
--dry-run.
--dry-run will load the main class without initializing it (= without
running the static initializers) - otherwise it wouldn't quite
be a dry run. see:
http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/604fc0a43f5b#l1.22
(the 'false' parameter given to Class.forName())
best regards,
-- daniel
On Jul 11, 2016 9:41 PM, "Mandy Chung" <mandy.ch...@oracle.com> wrote:
On Jul 12, 2016, at 10:35 AM, Paul Benedict <pbened...@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
