Hi Jonas, Yes, this is a known issue. The problem is that in this particular case the dependency is checked by the javac. IDEA's dependency checker is not even started because of the errors reported by javac. Currently we have no ideas how to solve this problem efficiently. But IMHO this problems is a minor one - anyway you get some errors reported instead of silently "compiling" and reporting that everything is ok.
Best regards, Eugene Zhuravlev JetBrains, Inc / IntelliJ Software, http://www.intellij.com/ "Develop with pleasure!" ----- Original Message ----- From: "Jonas Kvarnstr�m" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 27, 2002 17:26 Subject: [Eap-list] Bug in dependency checker (or compiler?) (#611) > Consider the following classes and interfaces: > > public interface Foo { > public void method(); > } > public abstract class AbstractFoo implements Foo { } > public class SomeFoo extends AbstractFoo { > public void method() {} > } > > Compile this. Then change SomeFoo: > > public class SomeFoo extends AbstractFoo { > public void method() throws Exception {} > } > > You'll get a compiler error since Foo.method() doesn't throw Exception. > Change Foo: > > public interface Foo { > public void method() throws Exception; > } > > Information about the abstract methods inherited from Foo is apparently > stored in AbstractFoo, so AbstractFoo now needs to be recompiled -- but > IDEA doesn't realize this so ctrl-f9 will just give you the same > compiler error again and again until you rebuild the entire project or > realize there's an abstract intermediate class and recompile it manually. > > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
