build: run javadoc linter in local testing and CI #244
Labels
code health
Improve code readability, simplify maintenance and so on
good first issue
Good for newcomers
testing
I recently found that I'm unable to prepare a release (
mvn release:clean release:prepare -DpushChanges=false
) because of javadoc linter errors (see PR #243). It would be good to catch those errors (and also warnings) during development.I don't know how to run a javadoc linter separately from
release:prepare
. Maybe we need to extract necessary parts of oss-parent POM to our POM file: if so, this issue looks connected with #241.The text was updated successfully, but these errors were encountered: