Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failure with OpenJDK 17 #1696

Open
ebourg opened this issue Feb 5, 2021 · 3 comments
Open

Build failure with OpenJDK 17 #1696

ebourg opened this issue Feb 5, 2021 · 3 comments

Comments

@ebourg
Copy link

ebourg commented Feb 5, 2021

There is a build failure with OpenJDK 17 caused by javadoc errors:

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /<<PKGBUILDDIR>>/src/main/java/org/junit/runners/Parameterized.java:[125,3] error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
[ERROR] /<<PKGBUILDDIR>>/src/main/java/org/junit/Test.java:[31,3] error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
[ERROR] /<<PKGBUILDDIR>>/src/main/java/org/junit/ClassRule.java:[34,3] error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
[ERROR] /<<PKGBUILDDIR>>/src/main/java/org/junit/rules/ExpectedException.java:[19,3] error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
[ERROR] /<<PKGBUILDDIR>>/src/main/java/org/junit/Rule.java:[26,3] error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
[INFO] 5 errors
@marcphilipp
Copy link
Member

Thanks for reporting it! Do you have time to submit a PR to fix it?

@marcphilipp marcphilipp added this to the 4.13.2 milestone Feb 5, 2021
@ebourg
Copy link
Author

ebourg commented Feb 6, 2021

The easiest solution is to disable doclint, by setting -Xdoclint:none there https://github.com/junit-team/junit4/blob/main/pom.xml#L536 and below

@marcphilipp
Copy link
Member

@ebourg I misunderstood your original report to mean that it failed for you in a dependent project that somehow references JUnit classes in its Javadoc. What Maven commandline did you use to get the above output?

@marcphilipp marcphilipp removed this from the 4.13.2 milestone Feb 13, 2021
@marcphilipp marcphilipp added maven and removed bug labels Feb 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants