Weekends are when I might be devoting some time to this
Are there any more granular ways to suppress some warnings than at the
method level? We have lots of places where we, say, open a SolrCore
and don't close it, it's added to a list and closed later which is
correct behavior so needs to be
Great, thanks! Half the battle is often knowing it's possible
On Thu, Feb 1, 2018 at 10:48 AM, Robert Muir wrote:
> Yes it is important to do it incrementally.
>
> You can override ant properties in specific modules, by defining them
> to be something stricter before importing them from somew
Yes it is important to do it incrementally.
You can override ant properties in specific modules, by defining them
to be something stricter before importing them from somewhere else.
For example, analysis/icu has no warnings, so override the default
javac.args at the very top, before it "imports" t
