Javadoc

Javadoc is an API documentation generator for the Java programming language. Based on information in Java source code, Javadoc generates documentation formatted as HTML and via extensions, other formats. ^[1] Javadoc was created by Sun Microsystems and is owned by Oracle today.

The content and formatting of a resulting document are controlled via special markup in source code comments. As this markup is de facto standard and ubiquitous for documenting Java code, ^[2] many IDEs extract and display the Javadoc information while viewing the source code; often via hover over an associated symbol. Some IDEs, like IntelliJ IDEA, NetBeans and Eclipse, support generating Javadoc template comment blocks. ^[3] The @tag syntax of Javadoc markup has been re-used by other documentation generators, including Doxygen, JSDoc, EDoc and HeaderDoc.

Javadoc supports extension via doclets and taglets, which allow for generating different output formats and for static analysis of a codebase. For example, JDiff reports changes between two versions of an API.

Although some criticize Javadoc and API document generators in general, one motivation for creating Javadoc was that more traditional (less automated) API documentation is often out-of-date or does not exist due to business constraints such as limited availability of technical writers. ^[4]

Javadoc has been part of Java since its first release, and is often updated with each release of the Java Development Kit. ^[5]

Javadoc and the source code comments used by Javadoc, do not affect the performance of a Java executable since comments are ignored by the compiler.

Markup

Javadoc ignores comments unless they are specially marked. A Javadoc comment is marked with an extra asterisk after the start of a multi-line comment: /**. A comment block pertains to the symbol that follows the block.

An example of a class header block follows:

/** * Provides some service * @author Jill Smith <[e-mail]> * @version 1.6 * @since 1.2 */publicclassTest{}

For a method, the first line is a short description of the method. If more detail is warranted, then it may be followed by a longer description in additional paragraphs. Following that are optionally various tags.

Various aspects of HTML as supported via Javadoc. For example <p> denotes a paragraph break.

An example of a method header block follows:

/** * One-line description * <p> * Longer description. If there were any, it would be here. * <p> * And even more explanation to follow in consecutive * paragraphs separated by paragraph break. * * @param variableName Description... * @return Description... */publicintmethodName(...){...}

Variables can also be documented. For example:

/** * Description of the variable here */privateintdebug=0;

A more complete example follows:

/** * Validates a chess move * * <p>Use {@link #doMove(int fromFile, int fromRank, int toFile, int toRank)} to move a piece. * * @param fromFile file from which a piece is being moved * @param fromRank rank from which a piece is being moved * @param toFile file to which a piece is being moved * @param toRank rank to which a piece is being moved * @return true if the move is valid, otherwise false * @since 1.0 */booleanisValidMove(intfromFile,intfromRank,inttoFile,inttoRank){...}/** * Moves a chess piece * * @see java.math.RoundingMode */voiddoMove(intfromFile,intfromRank,inttoFile,inttoRank){...}

Doclets

A Doclet program works with Javadoc to select which content to include in the documentation, format the presentation of the content and create the file that contains the documentation. ^[6] A Doclet is written in Java and uses the Doclet API ,

The StandardDoclet included with Javadoc generates API documentation as frame-based HTML files. Other Doclets are available on the web ^{[ citation needed ]}, often for free. These can be used to:

• Create other types of documentation (non-API)
• Output to a format other than HTML; such as PDF
• Output as HTML with additional features such as a search or with embedded UML diagrams generated from the Java classes

Tags

Some of the available Javadoc tags ^[7] are listed in the table below:

Syntax	Usage	Applies to	Since
@authorname	Identifies the author such as "Pat Smith"	Class, Interface, Enum
{@docRoot}	Represents the relative path to the generated document's root directory from any generated page	Class, Interface, Enum, Field, Method
@versionversion	Version information	Module, Package, Class, Interface, Enum
@sincesince-text	Describes when this functionality first existed	Class, Interface, Enum, Field, Method
@seereference	Links to other element of documentation	Class, Interface, Enum, Field, Method
@paramname description	Describes a method parameter	Method
@returndescription	Describes the return value	Method
@exceptionclassname description @throwsclassname description	Describes an exception that may be thrown from this method	Method
@deprecateddescription	Marks the method as outdated	Class, Interface, Enum, Field, Method
{@inheritDoc}	Copies the description from the overridden method	Overriding Method	1.4.0
{@linkreference}	Link to other symbol	Class, Interface, Enum, Field, Method
{@linkplainreference}	Identical to {@link}, except the link's label is displayed in plain text than code font	Class, Interface, Enum, Field, Method
{@value#STATIC_FIELD}	Return the value of a static field	Static Field	1.4.0
{@codeliteral}	Formats literal text in the code font; equivalent to {@literal}	Class, Interface, Enum, Field, Method	1.5.0
{@literalliteral}	Denotes literal text; the enclosed text is interpreted as not containing HTML markup or nested javadoc tags	Class, Interface, Enum, Field, Method	1.5.0
{@serialliteral}	Denotes a default serializable field	Field
{@serialDataliteral}	Denotes data written by the writeObject( ) or writeExternal( ) methods	Field, Method
{@serialFieldliteral}	Denotes an ObjectStreamField component	Field

See also

• Comparison of documentation generators
• .NET XML documentation comments

References

1. "Javadoc". agile.csc.ncsu.edu. Archived from the original on 13 June 2017. Retrieved 12 January 2022.
2. "javadoc - The Java API Documentation Generator". Sun Microsystems . Retrieved 2011-09-30..
3. IntelliJ IDEA, NetBeans Archived 2017-04-05 at the Wayback Machine and Eclipse
4. Venners, Bill; Gosling, James; et al. (2003-07-08). "Visualizing with JavaDoc". artima.com. Retrieved 2013-01-19. When I did the original JavaDoc in the original compiler, even the people close around me pretty soundly criticized it. And it was interesting, because the usual criticism was: a good tech writer could do a lot better job than the JavaDoc does. And the answer is, well, yeah, but how many APIs are actually documented by good tech writers? And how many of them actually update their documentation often enough to be useful?
5. "How to Write Doc Comments for the Javadoc Tool". Sun Microsystems . Retrieved 2011-09-30..
6. "Doclet Overview".
7. JavaSE 13 Documentation Comment Specification

External links

• Java Platform, Standard Edition Javadoc Guide
• JSR 260 Javadoc Tag Technology Update Java Specification Request (defines new Javadoc tags)
• Improve on Javadoc with ashkelon
• Various Java documentations converted to Windows Help format