+ Javadoc comment is multiline comment that starts with * character and placed under class definition, interface definition, enum definition, method definition or field definition.
+ The comment should be written in XHTML to be correctly processed by Checkstyle. This means that every HTML tag should have matching closed HTML tag or it is self-closed one (singlton tag).
+ The only exceptions are <p>, <li>, <tr>, <td>, <th>, <body>, <colgroup>, <dd>, <dt>, <head>, <html>, <option>,
+ <tbody>, <thead>, <tfoot> and Checkstyle won't show error about missing closing tag, however, it leads to broken XHTML structure and, therefore,
+ incorrect Abstract Syntax Tree of the Javadoc comment anyway. See examples at "HTML Code In Javadoc Comments" chapter.
+
+
+
- To start implementing your own Check create new class and extend AbstractJavadocCheck. It has two abstract methods:
+ To start implementing your own Check create new class and extend AbstractJavadocCheck. It has two abstract methods:
getDefaultJavadocTokens() - return array of token types that your new Check requires to process (see "Token Types" section)
+ Examples:
+ 1) Unclosed paragraph HTML tag. As you see in the tree, content of the paragraph tag is not nested to this tag. That is because HTML tags are not closed by pair tag </p>, and Checkstyle requires XHTML to correctly parse Javadoc comments.
+
+
+
+
+ 2) Here is correct version with open and closed HTML tags.
+