Bug 185322 - Method import can cause trouble during resolution
Summary: Method import can cause trouble during resolution
Status: VERIFIED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.6 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-03 07:42 EDT by David Audel CLA
Modified: 2009-08-03 08:52 EDT (History)
1 user (show)

See Also:


Attachments
Project to reproduce the problem (2.75 KB, application/octet-stream)
2007-05-03 07:43 EDT, David Audel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Audel CLA 2007-05-03 07:42:42 EDT
build I20070503-0010

import static q.Y.foo1;
public class Test {
	void bar(){
		Zork z = null;
	}
}

'Y' is a binary type and the return type of Y#foo1 is missing.

The Problem view show this problem:
The type p.X cannot be resolved. It is indirectly referenced from required .class

The editor show these problems:
The type p.X cannot be resolved. It is indirectly referenced from required .class
Zork cannot be resolved to a type
Comment 1 David Audel CLA 2007-05-03 07:43:13 EDT
Created attachment 65750 [details]
Project to reproduce the problem
Comment 2 Kent Johnson CLA 2007-05-09 13:57:37 EDT
This is done on purpose during a build.

We want to focus the user's attention on the classpath error so we remove all other errors from the project.
Comment 3 Olivier Thomann CLA 2009-06-25 15:25:04 EDT
Closing as WONTFIX
Comment 4 Frederic Fusier CLA 2009-08-03 08:52:29 EDT
Verified for 3.6M1