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 <j...@zeus.net.au> 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.
