Bug 271289 - [search] Workspace search not identifying equal packages
Summary: [search] Workspace search not identifying equal packages
Status: VERIFIED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.6 M1   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-06 04:48 EDT by Nobody - feel free to take it CLA
Modified: 2009-08-04 02:50 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nobody - feel free to take it CLA 2009-04-06 04:48:21 EDT
Build ID: 3.4.2 M20090211-1700

Steps To Reproduce:
1. Create a workspace containing two projects of Java code with project A referring to an interface FromB in project B. Ensure that project B has an implementation of FromB.
2. Build project B into B.jar.
3. Add B.jar to the build path of project A.
4. Navigate to interface FromB from project B. Select "FromB" and search the workspace for references to FromB. Only those references in project B are found, which is counter-intuitive for a workspace-wide search.
5. Navigate to FromB.class via the build path of project A. Select "FromB" and search the workspace for references to FromB. The references in project A and project B are found, which is what I would have expected in step 4.


More information:
http://www.eclipse.org/newsportal/article.php?id=24232&group=eclipse.tools.jdt#24232
Comment 1 Frederic Fusier CLA 2009-06-19 07:22:40 EDT
That works as expected. You would get a reference in project A if it did depend on project B otherwise, the FromB interface referenced in project B is only the one defined in this project, hence the difference between the two searches...

So, close as INVALID
Comment 2 Srikanth Sankaran CLA 2009-08-04 02:50:53 EDT
Verified for 3.6M1