-Xlog and the module system

Nicolai Parlog nipa at codefx.org
Thu Feb 2 10:59:53 UTC 2017


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

 Hi Alan.

> The trace messages emitted by -Xdiag:resolver are printed as the 
> resolver runs.

I'm sorry for being such a noob but my Google Foo failed at telling me
how to turn trace on for -Xdiag. :( Can you help me out?

 so long ... Nicolai



On 02.02.2017 09:07, Alan Bateman wrote:
> On 01/02/2017 21:49, Nicolai Parlog wrote:
> 
>> Hi Alan,
>> 
>> `-Xdiag:resolver` is awesome! :) I think these messages are
>> great candidates for info-level messages with the "modules" tag
>> via unified logging.
> I agree it should be transparent to developers using the JDK as to 
> whether the implementation is in libjvm or else where, something
> that will likely more of an issue going forward when more of the
> run time is written in the Java Language.
> 
>> 
>> Something else I noticed, neither Xlog nor Xdiag help with
>> problematic configurations - both only start logging after
>> everything checked out, so with missing modules (for example),
>> they do not provide additional information.
> The trace messages emitted by -Xdiag:resolver are printed as the 
> resolver runs. So aside from the initial module then they would see
> some output when transitive dependences can't be found.
> 
> -Alan
> 

- -- 

PGP Key:
    http://keys.gnupg.net/pks/lookup?op=vindex&search=0xCA3BAD2E9CCCD509

Web:
    http://codefx.org
        a blog about software development
    https://www.sitepoint.com/java
        high-quality Java/JVM content
    http://do-foss.de
        Free and Open Source Software for the City of Dortmund

Twitter:
    https://twitter.com/nipafx
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJYkxEpAAoJEMo7rS6czNUJcDMP/jxplSA7wD957SM1UWhbJ3Bq
qcD6Zy/k4LWkQ3xkRhE8MYU9lHWnRpKSAJ9tn6hVx2xhNxyM26VwKr9mg6enrXNc
xJn6UgokC6ypjQZWR7fCd4mibPFUujc2RCptph//UpUx8FcGDRvGbEt3l9LGL4JH
tuJrtRc06RqQpa2zvIf6nwFV3XMO8N0bXag+vAFMWfLVWReSBO5yYx9NxeE4BEto
H0fqGaSFLUGQ55YRqST5d5i9vcgX4CyCW8PzraPTjQq7Y92YgY4HCHLdFwrbtjp2
uX77CbrmZcXZI81Q0Z5F83WHEaiox+2xz2hazFRzyT+OGvnjBco+CdpMZ7LLL7ZY
4mZzRfDrlWXbwEsUkxzvPiO1Bkk9mjRQ7I15J2PjqgYHgNgnFwuU1txUwwN46VaH
YZ18/oa74a90yiikARYBFi9RhkihCLFjMmWFAWJaZ8MHhR1kqQmU1warKXrqk6ui
WW4ypATOvBAl+Fn/STDU+U41vxZIBpPC6Q1V8KuRDF49HY7K5bGqdOK0MXrYWc/P
o7E5tEvVIUG/wljxZVDvtECidGEYf+Sz7NqLk+vbUT5Ckng1A7xuqBd1ycEZnoKy
Fvib7x49TXC9aKorJ2bEHS6YPenEzOCybthtB/I1AwibVUEulcmJ3erndFjHuwPv
q0Hq+U6ddlAy6Ivp8Lkf
=pXtb
-----END PGP SIGNATURE-----


More information about the jigsaw-dev mailing list