Should this work?
Alan Bateman
Alan.Bateman at oracle.com
Sun Aug 2 10:25:02 UTC 2015
On 01/08/2015 21:57, Michael Hall wrote:
>
> I can’t tell from that though what produced the requirement for
> java.desktop. -module options didn’t seem to show this either on a
> class by class basis.
Have you tried -verbose:class to print class-level dependences?
>
> Generally I have used something like…
> try {
> if (System.getProperty("os.name").equals("Mac OS X"))
> UIManager.setLookAndFeel("ch.randelshofer.quaqua.QuaquaLookAndFeel");
> else
> UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
> } catch (Exception e) {
> }
> Which means it wouldn’t use Aqua since I started doing pointing to the
> 3rd party laf. But I have been unable to find where I do that for this
> particular application. So you’d think I’d be getting default laf.
> What is that metal? It would surprise me if that’s what I’m using.
>
"ch.randelshofer.quaqua.QuaquaLookAndFeel" is a String so the static
analysis that jdeps does isn't going to report this as a dependency.
The Aqua LAF is in the java.desktop module and hopefully with
-verbose:class you will be able to see if you directly make use of the
com.apple.laf classes.
-Alan
More information about the jigsaw-dev
mailing list