Re: Classes "Dependency Walker"?

From:

Joshua Cranmer <Pidgeot18@verizon.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 03 Apr 2009 10:48:11 -0400

Message-ID:

<gr57jb$2k8$1@news-int2.gatech.edu>

Andreas Leitgeb wrote:

When restricting it to static dependencies, such an analysis is not at
all that infeasible. My first approach would be running
javap -verbose path.to.EachClass
and grep the constant table for lines like "^const #\d* = class "
and extract the mentioned class name from the eol-comment. This needs
to be done recursively for each other class thusly obtained, preferrably
making use of something like a HashSet to recognize classes that were
already handled or are being handled right now, since this dependency-
"tree" surely won't be loop-free.

It would probably be faster and easier to just open each class file and
read the constant pool to find class references, especially on very
large classes. An experienced programmer could probably throw together a
tool to do this in an afternoon--the hardest part is figuring out how to
format the output. :-)

--
Beware of bugs in the above code; I have only proved it correct, not
tried it. -- Donald E. Knuth