|
|
|||||||
|
Potentially interesting, but I remember everyone writing such tools for as long as I remember coding in Java. Anybody relying on scanning a "classpath" misses two points: (a) content in jar/zip archives on disk may or may not be related to classes that actually get loaded in a JVM (b) there is no such a thing as a well defined "classpath" in Java anymore. That may have been true for Java 1.0 and 1.1 but these days of several classloaders operating in any JVM, what is it? Every classloader has it own classpath, its own delegation parent, and its own delegation/loading/caching strategy. |