> On Aug 2, 2015, at 3:40 PM, Alan Bateman <[email protected]> wrote:
> The com.apple.laf.* classes are in the java.desktop module and are selected > and used on your behalf then you select the system LAF. Your code isn't > directly linking to these classes so this is why jdeps doesn't report them as > a dependency. Hopefully I can convince you that jdeps is doing the right > thing. I think in this case jdeps is missing the dependencies. It works out here because the missed dependencies get a free ride along with the other java.desktop swing classes. So you will get the classes you need which is what matters. If for whatever reason you are interested in analyzing the laf dependencies I don’t think jdeps will do much for you. Except going directly after a class by name will probably indicate what other laf classes it has dependencies on. jdeps is, as advertised, a static analysis tool. I am not saying it isn’t doing what it is supposed to do. There is no problem unless you have a lot of dynamic dependencies that it misses which you don’t pick up somehow through some other classes. Michael Hall
