Community
Participate
Working Groups
3.0RC1 I'll attach a project in which Test1 extends Test and calls super.run(), where run() does not exist in Test. The error is not reported as a persistent problem, but only as a temporary. (It was once in a state where the temporary problem was not reported either.) I could not manage to setup a new project with the same behaviour. There are 2 output folders, 2 source folders and an exlusion filter on one source folder.
Created attachment 11450 [details] The described project.
There is something wrong with that project (it works in other projects): - if I create a JUnit Test with the New JUnit Test Case wizard, add a test method and try to run the whole Test, I get "Class not found org.test.SomeTest" on the console - if I add a main() method to Test and try to run Test as a Java Application, I get: "java.lang.NoSuchMethodError: main Exception in thread "main" on the console.
The test project has the Java builder disabled. Therefore it is no longer compiled, and thus doesn't induce any marker. You can observe though that the Java editor is correctly detecting the problem (which internally calls some compiler API to find problems). So basically, you never build .class files any longer. Checked that re-enabling the Java builder again works as expected.
