<target name="javadocs" depends="compile"> <javadoc sourcepath="${src}" packagenames="org.umlgraph.doclet.*" destdir="${javadoc}" private="true"> <doclet name="org.umlgraph.doclet.UmlGraphDoc" path="${lib}/UMLGraph.jar"> <param name="-inferrel"/> <param name="-inferdep"/> <param name="-hide" value="java.*"/> <param name="-collpackages" value="java.util.*"/> <param name="-qualify"/> <param name="-postfixpackage"/> <param name="-nodefontsize" value="9"/> <param name="-nodefontpackagesize" value="7"/> <param name="-link" value="http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/doclet/spec"/> <param name="-link" value="http://java.sun.com/j2se/1.5/docs/api"/> </doclet> </javadoc> </target>When generating documentation with UmlGraphDoc you will encounter at some point the "fur ball" effect: some central classes that have very complex context diagrams. To reduce this, you can avoid dependency inference altogheter, or reduce the number of inferred dependencies by using the -inferdepvis options. If you find that this is not enough and have suggestions on how to improve the situation further, we are eager to listen.
Contents | « Previous Next (Class Diagram Views) » |