Hi Alan,
`-Xdiag:resolver` is awesome! :) I think these messages are great
candidates for info-level messages with the "modules" tag via unified
logging.
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.
> We will probably re-visit this output at some point but there are
> other issues to clear away first.
I can understand that logging might not be the most pressing feature
this close to the release. :)
so long ... Nicolai
On 01.02.2017 18:20, Alan Bateman wrote:
> On 01/02/2017 14:27, Nicolai Parlog wrote:
>
>> Hi!
>>
>> When playing with `-Xlog:modules*` (down to trace) I hoped for a
>> little more output that I could use to analyze a configuration.
> -Xlog:modules is VM oriented and mostly traces the primitives used to
> construct the module graph in the VM.
>
> -Xdiag:resolver is probably closer to what you are looking for. We will
> probably re-visit this output at some point but there are other issues
> to clear away first.
>
> -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
