Bug 120350 - [model] Secondary type not found by code resolve
Summary: [model] Secondary type not found by code resolve
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M4   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 92486 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-12-12 05:13 EST by Jerome Lanneluc CLA
Modified: 2006-10-06 13:48 EDT (History)
2 users (show)

See Also:


Attachments
Patch to fix this issue (5.71 KB, patch)
2005-12-12 13:03 EST, Frederic Fusier CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2005-12-12 05:13:46 EST
I20051206 + latest JDT Core

1. Create file X.java
public class X {
}
class Y {
}
2. Create file Z.java
public class Z extends Y {
}
3. Have only Z.java editor open
4. Select Y
5. Press F3
Observe: No Java element is found
Comment 1 Frederic Fusier CLA 2005-12-12 13:03:32 EST
Created attachment 31571 [details]
Patch to fix this issue

Specific eclipse patch format including 2 projects:
  - org.eclipse.jdt.core
  - org.eclipse.jdt.core.tests.model
Comment 2 Frederic Fusier CLA 2005-12-12 13:11:29 EST
Search was also concerned while using searchDeclarationsOf* methods (ie. refactoring...).
Fix is small enough and safety to be a good candidate for M4...

All Java Model, DOM, Refactoring tests pass.

Philippe, Jerome, what's your mind about it?
Comment 3 Philipe Mulet CLA 2005-12-12 15:24:11 EST
+1 for M4. I assume the fix ensures it doesn't wait on indexing activity.
Comment 4 Frederic Fusier CLA 2005-12-12 16:58:37 EST
Yes, neither SelectionRequestor nor MatchLocator are waiting for indexing.
Comment 5 Frederic Fusier CLA 2005-12-12 17:48:38 EST
Patch released in HEAD.
Comment 6 Jerome Lanneluc CLA 2005-12-13 12:39:49 EST
Verified for 3.2 M4 using build I20051213-0010
Comment 7 Olivier Thomann CLA 2006-10-06 13:48:33 EDT
*** Bug 92486 has been marked as a duplicate of this bug. ***