The latest build log contains some Javadoc warnings that should be fixed.
Once that is done, I propose to treat Javadoc warnings as errors in the CI build as an easy way to automatically reject obvious inconsistencies (e.g., @param vs. actual method signature such as #411) or broken references.
The latest build log contains some Javadoc warnings that should be fixed.
Once that is done, I propose to treat Javadoc warnings as errors in the CI build as an easy way to automatically reject obvious inconsistencies (e.g.,
@paramvs. actual method signature such as #411) or broken references.