Bug 5007

Summary: Project classpath references do not follow class folders
Product: [Eclipse Project] JDT Reporter: Jed Anderson <jed.anderson>
Component: CoreAssignee: Kent Johnson <kent_johnson>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 2.0   
Target Milestone: 2.0 M1   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Jed Anderson CLA 2001-10-15 21:14:29 EDT 
Setup:
Project A


If I have two projects, A & B and A has a class folder which contains the
package foo and the class (in foo) foo.Bar
Comment 1 Jed Anderson CLA 2001-10-15 21:21:49 EDT 
Sorry, tab+enter did me in.  I'll try and finish my bug reports before I submit
them in the future :).

Setup:

Project A: contains compilation unit FooBar.java

public class FooBar {
  public void foo() {
    new foo.Bar();
  }
}
Project B: contains _class_folder_ classes, in classes is package foo, in foo is
classfile Bar.class

The compilation error message in the task list is "foo cannot be resolved or is
not a type".

Now add project B to the classpath of project A.  The error does not go away,
even though foo.Bar is clearly a part of project B.
Comment 2 Kent Johnson CLA 2001-12-10 17:04:11 EST 
Closed - not reproducable with new builder.

All classpath changes using the new builder result in the entire project being 
rebuilt.