-
Bug
-
Resolution: Fixed
-
P4
-
1.2.0
-
1.2beta4
-
x86
-
windows_nt
-
Verified
Name: rm29839 Date: 03/05/98
With version 1.1.5, if there was an unresolved
reference, javadoc simply didn't include
information on the unresolved reference in the
generated docs. This is the correct behavior.
javadoc 1.2, doesn't generate any docs! This is
a very serious problem. I do not include some
.java files in the path because I don't want them
to be documented for customers. Further, if it
can't find references to Sun's APIs, it also dies.
I don't want Sun's API docs filling up my docs!
Put it back to the way it was!!!
(Review ID: 25965)
======================================================================
With version 1.1.5, if there was an unresolved
reference, javadoc simply didn't include
information on the unresolved reference in the
generated docs. This is the correct behavior.
javadoc 1.2, doesn't generate any docs! This is
a very serious problem. I do not include some
.java files in the path because I don't want them
to be documented for customers. Further, if it
can't find references to Sun's APIs, it also dies.
I don't want Sun's API docs filling up my docs!
Put it back to the way it was!!!
(Review ID: 25965)
======================================================================
- relates to
-
JDK-4445752 when not able to resolve a symbol, Javadoc gives fatal error
-
- Closed
-