Checkstyle can be used to enforce the presence of javadoc.
At least the Travis CI build executes checkstyle and fails if checkstyle
fails.
Am 05.09.2019 um 18:04 schrieb sebb:
Can the CI build be changed to fail the build when Javadoc is omitted?
On Thu, 5 Sep 2019 at 17:00, Gary Gregory <garydgreg...@gmail.com> wrote:
Hi All:
The following interfaces were added a while back without class-level
Javadoc:
org.apache.commons.lang3.Functions.FailableBiConsumer<O1, O2, T extends
Throwable>
org.apache.commons.lang3.Functions.FailableBiFunction<I1, I2, O, T extends
Throwable>
org.apache.commons.lang3.Functions.FailableBiPredicate<O1, O2, T extends
Throwable>
org.apache.commons.lang3.Functions.FailableCallable<O, T extends Throwable>
org.apache.commons.lang3.Functions.FailableConsumer<O, T extends Throwable>
org.apache.commons.lang3.Functions.FailableFunction<I, O, T extends
Throwable>
org.apache.commons.lang3.Functions.FailablePredicate<O, T extends Throwable>
org.apache.commons.lang3.Functions.FailableRunnable<T extends Throwable>
org.apache.commons.lang3.Functions.FailableSupplier<O, T extends Throwable>
Would the original author, Jochen, or someone... chip in (again) please?
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
