Bug 65263

Summary:

Error not reported by compiler

Product:

[Eclipse Project] JDT

Reporter:

Christof Marti <christof_marti>

Component:

Core

Assignee:

Philipe Mulet <philippe_mulet>

Status:

RESOLVED INVALID

QA Contact:

Severity:

normal

Priority:

Version:

3.0

Target Milestone:

3.0 RC3

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
The described project.	none

Description Christof Marti

2004-06-02 06:33:31 EDT

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.

Comment 1 Christof Marti

2004-06-02 06:34:35 EDT

Created attachment 11450 [details]
The described project.

Comment 2 Christof Marti

2004-06-02 08:15:26 EDT

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.

Comment 3 Philipe Mulet

2004-06-15 06:29:58 EDT

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.