Ringo De Smet wrote:
> > > It would be nice to have a plug-in that would tell you the
> > dependencies within
> > > your project, so that you could easily know all the other
> > project members that
> > > call a certain part of the code. I'm imagining JBrowse,
> > parsing the entire
> > > project, with the ability to show "references" and
> > "referenced by" classes,
> > > methods, fields, macros, etc...
> > How about javadoc? It's not a plugin, but it will tell you all
> > the
> > 'uses' and 'used by' for each method in every class it
> > documents (in a
> > session).
>The use and used by features of JavaDoc only document usage of
>Java types as argument of return types. If you use a method
>within another method, this is not documented by JavaDoc. The
>only tool that can show all the references, referenced by, etc.
>for Java code is IBM VisualAge for Java. VAJ has an incremental
>compiler whenever I save a piece of code. After every change I
>see directly if dependencies are broken.
>I like jEdit very much as an editor, but it can't compete
>against VAJ for my Java development.
Ant comes with an optional task called "Depend", which
forces classes to be recompiled if they depend on a class
that has changed. That way, if your dependencies are broken,
you find out at compile-time instead of runtime. I know
that's a far cry from what you say VAJ does, but it's a start.
For instance, you could use Depend to generate the cached
dependency lists for the jEdit core and all the plugins,
then have a macro that scans those files and displays a list
of classes that depend on whatever file is in the current
buffer. Unfortunately, Depend doesn't store information about
methods, only classes, and of course this doesn't address the
problem of macro dependencies (which I seem to recall was the
original issue here), but, as I said, it's a start.