Fix Javadoc parsing issues for Checkstyle #21200
Open
+109
−99
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.
Summary
This PR fixes Javadoc issues exposed by the updated Checkstyle Javadoc parser, specifically in relation to
UnusedImportsCheck.Details
After updating Checkstyle, several Javadocs started failing parsing and caused false positives in
UnusedImportsCheck.The root cause is stricter Javadoc parsing introduced in Checkstyle (see checkstyle/checkstyle#18059), where malformed HTML and invalid
{@link}usages prevent the parser from correctly identifying type references.The fixes in this PR:
<ul>/<li>structures and unclosed tags).{@link}syntaxThere are no behavioral or API changes. All modifications are limited to Javadoc formatting and correctness.