Summary: | M5 build incorrectly reports unresolvable type errors for non-public classes in files with different name | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | John P. A. Verhaeg <jverhaeg> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | VERIFIED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | c.hauser, christof_marti, Frank.Cornelissen, nickell, sma |
Version: | 2.1 | ||
Target Milestone: | 3.2 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
John P. A. Verhaeg
2003-02-21 13:46:27 EST
This is a known issue when targeting secondary types. Note that these are usually not a good idea, since when performing incremental compilation, there is a chance that these files could be missing. We could fix this down the road by looking in every single compilation unit (mean open and parse contents to find these types). Though doable, the penalty hit would not be acceptable. Deferring (could use our index). *** Bug 34002 has been marked as a duplicate of this bug. *** *** Bug 36012 has been marked as a duplicate of this bug. *** *** Bug 32889 has been marked as a duplicate of this bug. *** This is also a problem for plugins--ITypeBinding.resolveTypeBinding() will return null. *** Bug 81155 has been marked as a duplicate of this bug. *** Reopen to close as duplicate *** This bug has been marked as a duplicate of bug 36032 *** Verified for 3.2 using M20060629-1905. |