chore(java): Clean up Javadoc warnings, and fail the build if any new ones are introduced#3477
Merged
chaokunyang merged 1 commit intoapache:mainfrom Mar 16, 2026
Merged
Conversation
stevenschlansker
force-pushed
the
javadoc-warnings
branch
4 times, most recently
from
3f40a11 to
2f6dd6c
Compare
… ones are introduced
stevenschlansker
force-pushed
the
javadoc-warnings
branch
from
2f6dd6c to
edcdf53
Compare
chaokunyang
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Javadoc build currently emits many warnings, which are lost in build output and ignored.
What does this PR do?
Fix the ones that are there, and turn on fail mode, so future warnings cannot be introduced.