Community
Participate
Working Groups
Build ID: I20070621-1340 Currently a parameter is reported as unused purely based on usage in that single method instance, which does not work very well if a superclass method does not use a parameter that a subclass method does. The "check overriding and implementing methods" option does not seem to rectify this. There is the option to ignore parameters documented with an @param tag, but this essentially amounts to nothing more than another form of @SuppressWarnings, which is not ideal since it allows you to hide instances where there really SHOULD be a warning. So, to summarize, it would be fantastic if there was an option to limit warnings to those instances where a parameter is unused in all subclass and superclass variants of a method. This would ensure that the warnings that are reported are always possible to act on by fixing the code.
Also, using @javadoc to hide these warnings, while better than nothing, gives rise to the problem where a method stops using a parameter but it's not reported as a warning because it's documented. This is probably going to happen fairly often, so it would be desirable to instead have a warning that never gives you a false positive so it can always be acted upon.
