Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
4.6
-
None
Description
During precommit we are seeing lots of warnings. Im turning this into an umbrella issue about getting precommit warnings out of the code in general. Yes, this will take a while.
See SOLR-10809 for getting all warnings out of solr/core. I want to selectively have precommit fail when "some part" of the code is clean so we don't backslide, and solr/core was the finest granularity I could see how to change.
If you read more of the comments here, you can see that there are some serious code refactoring that could be done. I'm electing to simply SuppressWarnings rather than re-arrange code at this point whenever the code is tricky. If anyone goes back in and tries to clean the code up, then can remove the annotation(s).
Attachments
Attachments
Issue Links
- incorporates
-
SOLR-11973 Fail compilation on warnings
- Resolved
- is a child of
-
SOLR-10810 Examine precommit lint WARNINGs in non-test code
- Resolved
-
SOLR-10809 Get precommit lint warnings out of Solr core
- Closed
- is related to
-
SOLR-10779 JavaBinCodec should use close consistently rather than having marshal() and close() call finish() (which closes the underlying stream)
- Resolved
-
LUCENE-7907 Ant precommit task WARNINGS about unclosed resources
- Resolved
-
LUCENE-9394 Fix or suppress compile-time warnings
- Closed
- relates to
-
LUCENE-9143 Add more static analysis and clean up resulting warnings/errors
- Resolved