javadoc和doxygen的对比

In this blog entry , Jared Odulio asks an interesting question: Do you still document your source with JavaDocs?

Two of the coolest Linux utilities that help us document our Java source codes areand . With these tools we can generate neat documentations with call graphs and summarized UML class diagrams in addition to just plainly hyperlinking who is subclassing or implementing what. The Call Graph is even cooler, future developers can easily read your code in terms of what method is invoking another method. Generated documents can be in html or pdf depends on your initial settings. 

With this kind of tool, it's a shame sun's javadoc tool hasn't advanced much in years. And saying that doing it for free is such a lame excuse. And what javadocs can do, Doxygen can do more. There even a Doxygen plugin for Eclipse, but what the heck command line is faster.

What do you think? Is Javadoc still doing the job for you? Do you prefer another tool for some reason? If so, which one and why? Since Javadoc is extensible, is it better to focus on building useful extension to Javadoc than to switch to completely different tools? Do you have any favorite Javadoc extensions?

通过以上文件，我们了解到，javadoc不能生产函数(方法)调用图。