Should we take this opportunity to clean up unneeded Throws declarations in our APIs?

[Marshall Schor]

Running Findbugs, etc., will report on throws / catches that are never 
used because the code in the try doesn't throw what is being caught or 
propagated up.

It might be good to clean these up.  Typically, they are not changed, 
because that kind of a change in an API breaks user code.  I'm wondering 
if we could clean these up and have the migration utility fix the user code?

Opinions?

-Marshall