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 FUNCTIONAL CODE WAS CHANGED. ALL CHANGES ARE STRICTLY API DOCUMENTATION.
While cleaning gradle and considering moving to Java 21 for building (still will target Java 8, but also may target Java 17 and Java 21 in separate jars), new versions of Javadoc are more particular about javadoc warnings.
• One of the most common was
Which requires change to include a description other than the return
• Another common one was constants did not have javadoc comments. It seemed redundant when well named.
• Another was objects with only no-parameter constructors, so in reality had no constructor code. Javadoc didn't like this so no-parameter constructors were made and javadoc'ed
• There were some legitimate missing api, but almost entirely self documenting setters and getters.