B. Troubleshooting: Bugs, Errors and Warnings

B1. What bugs are in Javadoc?

B2. How do I submit bugs and feature requests?

B3. How do I redirect error messages to a file?

B4. I just can't get Javadoc to work over my entire source code; what do you
suggest?

B5. I run out of memory -- how much is needed, exactly how do you call Javadoc, and
how long does it take?

B6. Why aren't the memory flags (-J-m) recognized in Windows?

B7. When I run Javadoc on my source package, some links are not generated.

B8. In Javadoc 1.2.2, when using @see or {@link} tags to external API, and links to
methods, fields and constructors are missing.

B9. Why do I get the warning "Class or Package not found in @see/@link tag" or "reference not found"?

B10. The class comments are missing from the generated docs, but are in the source
code.

B11. When I run Javadoc, I get the following exception warning: "Method X declares that it throws class Y, but there is no corresponding @exception item." What does this message mean?

B12. I copied all of my .java files from their package hierarchy into a single
directory so it would be easier to run Javadoc on them, but it doesn't work.

B13. I am documenting 33 packages and added a new package to my javadoc command but this created a "No source files" error.

B14. I get the error "Class xxx already defined".

B15. I get the errors "FileNotFoundException" and "Fatal Exception".

B16. Using Javadoc 1.4.1, I get an InvocationTargetException when I set the
classpath.

B17. Why do I get so many @serial warnings, including warnings about private fields?