I believe this warning is false, at least in some cases.
I have places where a field is initialized by a call to a method and where that field is used only in a single method, leading to the triggering of this inspection.
However, the inspection's validity seems to overlook possible side-effects, non-idempotency and execution costs of the method call used to supply the initializing value for the field in question.
Am I mistaken about this?
Edited by: Randall Schulz on Apr 29, 2008 12:25 PM — Changed the oxymoronic "local field" to "field" in the 2nd paragraph.