On 02/11/2022 15:52, Rémy Maucherat wrote:
Hi,
It seems javadoc has become a lot stricter moving forward (starting
with Java 18 it seems), where basically everything now needs a
javadoc. So will we be keeping a zero warning policy, or are we going
to decide to relax it ?
If not, this will keep up busy for some time ;)
I noticed the problem while looking at the github actions failures
with Java 18+ and seeing the javadoc output after fixing.
It depends what the minimum Java version for Jakarta EE 11 is ;)
More seriously, I have been slowly working through these over time with
the plan / hope to have fixed them by the time we absolutely have to. It
does seem to be a bit of a moving target depending on JVM vendor and
Java version.
We should parameterise failonerror and failonwarning so users can
compile more easily on later versions. And we can change default if we
reach a point we need to.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
