fix(javadoc): replace unknown Javadoc tags with standard equivalents - #573
Merged
NicolasAnquetil merged 2 commits intoSep 5, 2026
Conversation
Test Results 439 files 439 suites 21s ⏱️ Results for commit 533de5a. ♻️ This comment has been updated with latest results. |
remiceres
approved these changes
Sep 4, 2026
remiceres
left a comment
Contributor
There was a problem hiding this comment.
Reviewed and verified locally: Javadoc generation completes without unregistered custom-tag warnings.
|
NicolasAnquetil
approved these changes
Sep 5, 2026
NicolasAnquetil
left a comment
There was a problem hiding this comment.
This does solve the problem. Much cleaner build
NicolasAnquetil
deleted the
feature/555-unregistered-custom-tags-in-javadoc
branch
September 5, 2026 08:28
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
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.
No description provided.