Bug 85394 - [compiler] Strange error messages when a package declaration is missing
Summary: [compiler] Strange error messages when a package declaration is missing
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-16 07:11 EST by David Audel CLA
Modified: 2009-08-30 02:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Audel CLA 2005-02-16 07:11:09 EST
build I20050215-2300

1) create p2/B.java
//package p2;
public class B {
    void bar() {
    }
}

2) create p/A.java
package p;
public class A {
    public void foo() {
        new p2.B().bar();
    }
}

3) compile
The errors inside the problem view are:
"The method bar() from the type B is not visible" inside A.java
"The declared package does not match the expected package p2" inside B.java

The errors inside the editor are:
"p2.B cannot be resolved to a type" inside A.java
"The method bar() from the type B is not visible" inside A.java
"The declared package does not match the expected package p2" inside B.java

An error is missing in the problem view.
Errors inside the editor look strange. The first error says that B is not
resolved but the second error should appear only when B is resolved.
Comment 1 Philipe Mulet CLA 2005-04-07 09:44:27 EDT
Deferring post 3.1
Comment 2 Eclipse Webmaster CLA 2009-08-30 02:36:45 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.