Class MissingJavadocPackageCheck

  • All Implemented Interfaces:
    Configurable, Contextualizable

    public class MissingJavadocPackageCheck
    extends AbstractCheck

    Checks for missing package definition Javadoc comments in files.

    Rationale: description and other related documentation for a package can be written up in the file and it gets used in the production of the Javadocs. See link for more info.

    This check specifically only validates package definitions. It will not validate any methods or interfaces declared in the file.

    Parent is

    Violation Message Keys:

    • package.javadoc.missing
    • Method Detail

      • getAcceptableTokens

        public int[] getAcceptableTokens()
        Description copied from class: AbstractCheck
        The configurable token set. Used to protect Checks against malicious users who specify an unacceptable token set in the configuration file. The default implementation returns the check's default tokens.
        Specified by:
        getAcceptableTokens in class AbstractCheck
        the token set this check is designed for.
        See Also:
      • hasJavadoc

        private static boolean hasJavadoc​(DetailAST ast)
        Checks that there is javadoc before ast. Because of parser bug parser can place javadoc comment either as previous sibling of package definition or (if there is annotation between package def and javadoc) inside package definition tree. So we should look for javadoc in both places.
        ast - TokenTypes.PACKAGE_DEF token to check
        true if there is javadoc, false otherwise
      • hasJavadocAboveAnnotation

        private static boolean hasJavadocAboveAnnotation​(DetailAST ast)
        Checks javadoc existence in annotations list.
        ast - package def
        true if there is a javadoc, false otherwise
      • isJavadoc

        private static boolean isJavadoc​(DetailAST ast)
        Checks that ast is a javadoc comment.
        ast - token to check
        true if ast is a javadoc comment, false otherwise