[ https://issues.apache.org/jira/browse/LUCENE-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141102#comment-17141102 ]
Michael Sokolov commented on LUCENE-9394: ----------------------------------------- > Do you (or anyone else) want to weigh in on whether to backport this fix or > just SuppressWarnings in 8x for Lucene? I think it's down to what our back compat policy is. If we're OK with introducing breaking API changes in a minor release, then we should fix rather than suppress, but I was under the impression that we only made such changes on major releases. I personally feel this would be OK - it's a compilation failure, not a behavior change, so there's no risk someone gets a surprise; they just have to fix up their Map types or add SuppressWarnings. > Fix or suppress compile-time warnings > ------------------------------------- > > Key: LUCENE-9394 > URL: https://issues.apache.org/jira/browse/LUCENE-9394 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Michael Sokolov > Assignee: Michael Sokolov > Priority: Major > Fix For: master (9.0) > > Time Spent: 50m > Remaining Estimate: 0h > > This is a spinoff from [~erickerickson]'s efforts over in SOLR-10778 > The goal is a warning-free compilation, followed by enforcement of build > failure on warnings, with the idea of suppressing innocuous warnings to the > extent that the remaining warnings be treated as build failure. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org