Fix JavaDoc warnings and enforce zero errors in Gradle #2513
Conversation
This file contains 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
Now, we ensure that our JavaDoc doesn't produce any warnings. The most common problems were using < instead of < and & instead of the word "and".
TimvdLippe
commented
Dec 14, 2021
| @@ -6,7 +6,6 @@ | |||
| /** | |||
| * Integration to provide better support for IDEs that support OpenTest4J. | |||
| * | |||
| * @see org.mocktio.exceptions.verification.junit | |||
There was a problem hiding this comment.
We misspelled our own package name here 😄
We don't actually need this information anymore, as javadoc.io already adds the information.
|
I am merging this one as low-risk and mostly mechanical. |
xuelin2020
pushed a commit
to xuelin2020/mockito
that referenced
this pull request
Dec 28, 2021
Now, we ensure that our JavaDoc doesn't produce any warnings. The most common problems were using < instead of < and & instead of the word "and".
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.
Now, we ensure that our JavaDoc doesn't produce any warnings. The most
common problems were using < instead of < and & instead of the word
"and".