Bug 103139 - Wrong markers "...cannot be resolved to a type"
Summary: Wrong markers "...cannot be resolved to a type"
Status: RESOLVED DUPLICATE of bug 36032
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-08 05:26 EDT by Tom Zimmermann CLA
Modified: 2005-07-11 05:51 EDT (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 Tom Zimmermann CLA 2005-07-08 05:26:56 EDT
Eclipse creates wrong markers that say "Quux cannot be resolved to a type". Quux is a class that is 
defined in a file Bar.java with access level package private.

Sample code:

** File Bar.java **
class Quux {}

** File Foo.java **
public class Foo {
	public static void main(String[] args) {
		Quux a = new Quux();
	}
}

How to reproduce the failure:
1.) Create the two files Foo.java and Bar.java
2.) Restart Eclipse
3.) Open Foo.java first. There are no errors in the Problems View but the declaration "Quux a =..." has 
an error marker (actually two).
4.) Open Bar.java
5.) Go to the Foo.java editor
6.) The incorrect error markers have disappeared
Comment 1 Philipe Mulet CLA 2005-07-11 05:51:35 EDT

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