Skip to content

Eliminate all Javadoc warnings across the reactor#30

Open
herbie-bot wants to merge 1 commit into
mainfrom
fix/javadoc-warnings
Open

Eliminate all Javadoc warnings across the reactor#30
herbie-bot wants to merge 1 commit into
mainfrom
fix/javadoc-warnings

Conversation

@herbie-bot

Copy link
Copy Markdown
Collaborator

Summary

The -Pfull-build javadoc-jar goal (attach-javadocs) emitted ~260 doclint warnings across all nine modules — missing @param/@return, undocumented members, enum constants, record components, and uncommented default constructors. This documents every affected public/protected API element with meaningful Javadoc so the build is warning-free.

Changes

  • Meaningful Javadoc added across core, slack, search, dbbackup, email, mcp (116 files).
  • The only non-comment changes are behaviour-neutral explicit constructors (identical to the previously implicit ones) added to @Configuration/@AutoConfiguration classes, entities, and the ImageUtilities utility class (private), so the "use of default constructor" doclint warnings can carry a comment.
  • No method signatures, field types, annotations, or logic changed. No test code touched. Only .java files.

Verification

  • ./mvnw -o -Pfull-build clean verify: 0 javadoc warnings, BUILD SUCCESS, all tests green across the 9-module reactor.

Note

Two verification passes were needed because the plain javadoc:javadoc goal uses laxer doclint than the build's attach-javadocs execution; the final count is verified against the strict full-build goal that CI/release use.

🤖 Generated with Claude Code

The -Pfull-build javadoc jar goal (attach-javadocs) emitted ~260 doclint warnings
across all modules — missing @param/@return, undocumented members, enum constants,
record components, and uncommented default constructors. Documents every affected
public/protected API element with meaningful Javadoc.

Purely additive documentation: the only non-comment changes are behaviour-neutral
explicit constructors (identical to the previously implicit ones) added to
@Configuration/@autoConfiguration classes, entities, and the ImageUtilities utility
class, so the "use of default constructor" warnings can carry a comment. No method
signatures, field types, annotations, or logic changed; no test code touched.

Verified with `./mvnw -o -Pfull-build clean verify`: 0 javadoc warnings, all tests
green across the 9-module reactor.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants