P.S.
The real power, lies with the collection that's returned containing the
dependency relationships, once you have that collection, you can
manipulate the results.
Maybe that's where I need to be looking?
Cheers,
Peter.
Peter Firmstone wrote:
Hmm, Unix hey?
Svn update then build trunk.
ant classdepend.jar
Then from the trunk directory, run something like this:
java -jar lib/classdepend.jar -cp build/classes -graph -excljava
com.sun.jini.outrigger.PersistentOutriggerImpl >output_graph.txt
You'll need to add the following to the text file.
digraph G {
}
Sorry I hadn't added it to the output for the -graph option.
-excljava excludes classes from the java platform.
You can edit com.sun.jini.tool.classdepend.ClassDepend.java and create
a number of other command line options.
To see what can be done, there are a number of additional options
documented in com.sun.jini.tool.classdepend.ClassDependParameters.
These could be added quite simply to make the command line much more
powerful.
Cheers,
Peter.
Dan Creswell wrote:
JTree - possibly. My UNIX'y nature means I'd still like to be able to
run
the likes of GraphViz and so on.
On 22 January 2011 09:34, Peter Firmstone <[email protected]> wrote:
Ok, sounds like a good experiment, the interesting thing about River
packages, is they tend to originate from multiple jar files.
The code's been in River since the last release, since ClassDep
depends on
it, I've created a jar locally that allows you to run classdepend
from the
command line. I think I'll upload the changes so anyone interested
can play
around with it too.
The programmable API is more powerful than the command line api,
perhaps
classdepend needs a dynamic graphical api. JTree?
Cheers,
Peter.
Dan Creswell wrote:
How about we trim it down by considering only inter-package
dependencies
or
similar to start with?
Then maybe separate graphs for each package?
On 22 January 2011 09:05, Peter Firmstone <[email protected]> wrote:
Thanks Dan & Patricia for your suggestions,
I'm still struggling with the graph output, it's a lot of data,
perhaps
too
much, the PNG turned out to be 30MB, for all dependency links in
River,
originating from PersistentOutriggerImpl.
I've attached the text file used to generate the graph.
I'll have to get back to you.
Cheers,
Peter.
