Closed kbevers closed 4 years ago
Thanks for the patch. But maybe you are using Java 11? The header sequence has changed in Java 13, and the one used in the current source code is for Java 13. Note that even if compiling with Java 13, the code is still executable on Java 11.
Alternatively we could disable completely the sequence check. Actually this check is disabled by default and explicitly activated in this project; we could just remove that activation. Please let me know which approach you prefer (if you prefer to disable the check, just delete line 105 (<arg>-Xdoclint:all</arg>
) in the pom.xml
file.)
My java version seem to be 11:
$ java --version
openjdk 11.0.1 2018-10-16 LTS
OpenJDK Runtime Environment Zulu11.2+3 (build 11.0.1+13-LTS)
OpenJDK 64-Bit Server VM Zulu11.2+3 (build 11.0.1+13-LTS, mixed mode)
If this change causes problems in java 13 builds then I think the sequence check should be turned of. If it doesn't, then this patch should be applied.
It is not possible to have the checks enabled for both Java 11 and Java 13 as they conflict. I propose to keep master
as-is so the development stay strict with latest Java version, and remove all explicit "turn on" in the release. So the release would use default setting, which work fine with all supported versions.
If okay, I will created a 1.0-RC3 after we fixed other issues, and create a wiki page with release instructions in order to remember that.
Sounds good
I disabled the doclinting in pom.xml in #25
Running
mvn package
I get the following error:This PR fixes the problem by changing to
<h3>
headers