natas_hw
/
UMLGraph
mirror of https://github.com/dspinellis/UMLGraph
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix name into UmlGraphDoc (Stefan Birkner)

This commit is contained in:
Diomidis Spinellis 2006-07-26 14:34:36 +00:00
parent 60d6271d6d
commit 845d9fac0d
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/cd-umldoc.xml
View File

@ -1,11 +1,11 @@
<?xml version="1.0" ?>
<!-- $Id$ -->
<notes>
UMLGraphDoc is a standard doclet wrapper that combines
UmlGraphDoc is a standard doclet wrapper that combines
the standard doclet output (javadoc documentation) along with auto-generated
class diagrams for both packages and classes.
The UMLGraphDoc process is driven by all the parameters that can be specified for
The UmlGraphDoc process is driven by all the parameters that can be specified for
UMLGraph and the standard doclet; each will be passed to the appropriate
doclet.
@ -19,13 +19,13 @@ The actual content of the diagrams depends on the kind of relations declared on
class files (with the UMLGraph javadoc annotations) and/or on the kind of automated
inference that UMLGraph is allowed to use.
UMLGraph javadocs are now generated with UMLGraphDoc with the following ant target:
UMLGraph javadocs are now generated with UmlGraphDoc with the following ant target:
<fmtcode ext="xml">
<target name="javadocs" depends="compile">
<javadoc sourcepath="${src}" packagenames="gr.spinellis.umlgraph.doclet.*" destdir="${javadoc}"
private="true">
<doclet name="gr.spinellis.umlgraph.doclet.UMLGraphDoc" path="${lib}/UMLGraph.jar">
<doclet name="gr.spinellis.umlgraph.doclet.UmlGraphDoc" path="${lib}/UMLGraph.jar">
<param name="-inferrel"/>
<param name="-inferdep"/>
<param name="-hide" value="java.*"/>
@ -41,7 +41,7 @@ UMLGraph javadocs are now generated with UMLGraphDoc with the following ant targ
</target>
</fmtcode>
When generating documentation with UMLGraphDoc you will encounter
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