JavaDoc is a tool to explain to the public how to access the "application public interface". If the public can not get at the class - it will not be documented in the API. From javadoc - The Java API Documentation Generator.
The JavadocTM tool parses the declarations and documentation comments in a set of Java source files and produces a corresponding set of HTML pages describing (by default) the public and protected classes, nested classes (but not anonymous inner classes), interfaces, constructors, methods, and fields.
"JavaRanch, where the deer and the Certified play" - David O'Meara
Joined: Mar 06, 2002
Thanks! Is there a way to change my single file with the classes into a package with different files? I get always an error if I make a class to a .java file. For example the class "Statement" is not found, but i imported all i need...
Joined: Sep 29, 2000
Well, yeah. You would put each class in a separate file, and add a package statement to each file, then make sure that the files reside in a subdirectory with the name of that package until you get it jarred up. Of course that is not really going to affect your JavaDoc unless you also make the classes public or protected.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com