There are about 100 compile-time warnings in Lucene, not including deprecations. I’m trying to get all the warnings out or suppressed so we can stop backsliding by turning up compilation errors to include selected warnings.
But I don’t want to muck with Lucene without some consensus on whether this idea is A Good Thing. So for you folks who work in Lucene a lot, would this be valuable? Or should I just ignore Lucene? I want to emphasize that all I’m really doing at this point is adding bunches of SuppressWarnings and a few safe changes, things like removing redundant casts and the like. There are just too many warnings in the code base to try to do all at once, and it’s usually a bad idea to make wholesale code changes when the code is working. A separate question is whether to enable compile-time errors on warnings (probably master only) that we can save for later. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
