Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The JavaDoc is not part of a Java program. So you have to bundle the resources with your program regardless of what approach you use.</p> <p>So you have two possibilities:</p> <ol> <li><p>Generate the documentation with javadoc and bundle the result. It is easy to see how to map from a class name to the html page by looking at the generated files. The JavaDoc documentation (the Default doclet’s documentation to be more precise) contains more detailed descriptions</p></li> <li><p>If you want to generate the documentation on-the-fly you have to bundle the source code with your application. Further, your application have to run inside a JDK rather than a plain JRE to get hands on JavaDoc.</p></li> </ol> <p>See <a href="http://docs.oracle.com/javase/7/docs/technotes/guides/javadoc/standard-doclet.html" rel="nofollow">http://docs.oracle.com/javase/7/docs/technotes/guides/javadoc/standard-doclet.html</a></p> <blockquote> <p>Running the Standard Doclet Programmatically</p> <p>The Javadoc tool has a programmatic interface with public methods for invoking the Javadoc tool from another program written in the Java language. These methods are located in class com.sun.tools.javadoc.Main in lib/tools.jar. …</p> <p>public static int execute(String programName, PrintWriter errWriter, PrintWriter warnWriter, PrintWriter noticeWriter, String defaultDocletClassName, String[] args)</p> </blockquote> <p>This execute method is overloaded with variants taking fewer parameters.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload