Bug 87063 - [reconciling] The java file editor showing error marks while no error is there
Summary: [reconciling] The java file editor showing error marks while no error is there
Status: RESOLVED DUPLICATE of bug 36032
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.2 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-03 08:12 EST by Sobia CLA
Modified: 2006-03-27 10:09 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sobia CLA 2005-03-03 08:12:39 EST
The java file opened in the java editor is marked with errors and warnings. 
Whereas the Problems tab is blank and does not show any problems. The project 
runs well; which means there are no errors there really.

The build automatically option is ON, so that cannot be the problem. The error 
marks are not removed on refreshing or saving the file either.
Comment 1 Tom Hofmann CLA 2005-03-03 14:02:07 EST
Can you give concrete steps on how to reproduce what you are seeing? I cannot
reproduce with M5a.

See also
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-text-home/development/bug-annotation.htm
Comment 2 Sobia CLA 2005-03-04 07:48:16 EST
(In reply to comment #1)
> Can you give concrete steps on how to reproduce what you are seeing? I cannot
> reproduce with M5a.
> See also
> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-text-
home/development/bug-annotation.htm

See the following points:
- The "Build Automatically" option is ON.
- I am using the JAVA perspective.
- I created a new project and imported some existing project code into it.
- There were errors due to the required libraries not found.
- The output folder for the project was changed.
- The required libraries were provided
- Now the Problems tab was not showing any problems and the project was running 
fine, but few files were continously showing the error marks (The red crosses 
and waivy underlines) as if there were errors.
- Refreshing and saving the files even re opening the Eclipse did not remove 
the marks.

It might be either due to the output folder change because refreshing problem 
might have been solved when Eclipse was reloaded.

Hope this information would help you.
Comment 3 Dani Megert CLA 2005-03-08 09:38:49 EST
>Problems tab
Which Problems tab?

Was the file open before you changed the build path/output folder?
Comment 4 Dani Megert CLA 2005-03-08 09:40:13 EST
Can you attach a screen shot?
Comment 5 Sobia CLA 2005-05-30 10:51:34 EDT
The java file editor shows the red error marks while the code gets compiled and 
runs successfully. The problem pane is not showing the description of the 
errors. The Package Explorer does not mark the file with error mark and the 
header (mentioning the name of file) of the editor tab does not show the error 
icon as well.
Detail of ERROR:
There are multiple classes defined in a single java file. The additional 
classes are "default" i.e. there is no access modifier attached. The editor 
marks the code with errors wherever the default classes are accessed. The error 
is: "<Default class name> cannot be resolved for the method <methos name>". The 
pop-up options like "Open Call Hierarchy" do not work properly while this error 
is showing up. The code compiles and runs without any problem that shows it is 
not a real ERROR.
Comment 6 Dani Megert CLA 2005-05-30 11:34:10 EDT
>There are multiple classes defined in a single java file. The additional 

OK, I see what you mean. Simple test case:

1. have CU A with public class A and second class B
2. have CU C which uses B
==> editor reports error if C is opened in the Java editor.

Those are temporary problems reported by Java Core.
Comment 7 Dani Megert CLA 2005-06-06 12:14:58 EDT
*** Bug 98505 has been marked as a duplicate of this bug. ***
Comment 8 Frederic Fusier CLA 2006-03-27 10:07:26 EST

*** This bug has been marked as a duplicate of 36032 ***