Missing Javadoc
ID |
java.missing_javadoc |
Severity |
low |
Remediation Complexity |
auto_fix |
Remediation Risk |
low |
Remediation Effort |
low |
Resource |
Documentation |
Language |
Java |
Tags |
best-practice, documentation |
Description
Reports declarations that lack a Javadoc comment or whose Javadoc is missing required tags.
Public APIs should be documented with Javadoc so that consumers can understand the contract without reading the implementation. Missing @param, @return, or @throws tags force readers to guess parameter semantics, return values, and error conditions.
|
This rule does not apply to files under paths configured in |
Rationale
-
Maintainability – Undocumented public APIs slow down onboarding and increase the chance of misuse.
-
Tooling – IDEs and documentation generators rely on Javadoc to provide inline help and API reference pages.
Configuration
The rule is fully configurable. Properties control which declarations require Javadoc and which tags must be present.
Declaration checks
| Property | Default | Description |
|---|---|---|
|
|
Require Javadoc on public classes, interfaces, enums, records |
|
|
Require Javadoc on protected types |
|
|
Require Javadoc on private types |
|
|
Require Javadoc on public methods and constructors |
|
|
Require Javadoc on protected methods |
|
|
Require Javadoc on private methods |
|
|
Require Javadoc on public fields |
|
|
Require Javadoc on protected fields |
|
|
Require Javadoc on private fields |
Tag requirements
When a method or constructor has Javadoc, these properties control which tags must be present.
| Property | Default | Description |
|---|---|---|
|
|
Require |
|
|
Require |
|
|
Require |
|
|
Require |
|
|
Require |
|
|
Require |
|
|
Require |