consider the following:

class Foo {
   abstract void execute() throws Exception;
}

class Bar extends Foo {
   void execute() throws java.io.IOException {
      throw new java.io.IOException("Bar");
   }
}

In this example, the subclass is overriding the
superclass's method. However, the "Override
Methods" feature will repeatedly complain that
class Bar needs to implement 
"abstract void Foo::execute() throws Exception",
even though it already is overriding it.

I believe, that the "Override Methods" feature
needs to recognize the situations where the
subclass's method has a more specific (less
general) exception specification than the declared
method it is overriding.