[ 
https://issues.apache.org/jira/browse/LUCENE-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316345#comment-17316345
 ] 

ASF subversion and git services commented on LUCENE-9912:
---------------------------------------------------------

Commit bda608f6e022841a2a93bdaabdc4646bf0289445 in lucene-solr's branch 
refs/heads/branch_8_8 from Uwe Schindler
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=bda608f ]

LUCENE-9912: Fix some broken HTML that make javac/javadoc fail in Java 17


> Disable HTML doclint in Lucene/Solr 8
> -------------------------------------
>
>                 Key: LUCENE-9912
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9912
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 8.x, 8.8.1
>         Environment: openjdk version "17-ea" 2021-09-14
> OpenJDK Runtime Environment (build 17-ea+16-1315)
> OpenJDK 64-Bit Server VM (build 17-ea+16-1315, mixed mode, sharing)
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>            Priority: Blocker
>              Labels: Java17
>             Fix For: 8.x, 8.8.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Due to LUCENE-9209 we fixed most of the Javadocs in Lucene / Solr master/main.
> But we did not do that in Lucene 8. Unfortunetaly later Java versions (JDK 
> 17) now fail to compile or run javadoc, because the later java versions apply 
> very strict HTML5  checks.
> The main problem again is thet we unconditinally enable {{-Werror}} at the 
> same time with {{-Xdoclint:all}} (as said hundreds of times by me, we should 
> really only enable warnings we know of!).
> To allow compilation with JDK-17 or later I will remove the HTML warnings 
> from the config



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to