[
https://issues.apache.org/jira/browse/LUCENE-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated LUCENE-7631:
------------------------------
Attachment: LUCENE-7631.patch
Patch that ensures we won't add any new compiler warnings in several categories
(that we're pretty good on already) in the future. We can deal with fixing
existing rawtypes or a few other classes of warning in the future.
[~dsmiley] - you seemed interested in this conversation last time it came up.
> Enforce javac warnings
> ----------------------
>
> Key: LUCENE-7631
> URL: https://issues.apache.org/jira/browse/LUCENE-7631
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/build
> Reporter: Mike Drob
> Attachments: LUCENE-7631.patch
>
>
> Robert's comment on LUCENE-3973 suggested to take an incremental approach to
> static analysis and leverage the java compiler warnings. I think this is easy
> to do and is a reasonable change to make to protect the code base for the
> future.
> We currently have many fewer warnings than we did a year or two years ago and
> should ensure that we do not slide backwards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
