Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359519 - EGL Search: Annotation search will miss some expected results
Summary: EGL Search: Annotation search will miss some expected results
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Zhi Zhu CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-30 02:41 EDT by Thomas Wu CLA
Modified: 2017-02-23 14:14 EST (History)
3 users (show)

See Also:

Attachments
PI (367.14 KB, application/x-zip-compressed)
2011-09-30 02:42 EDT, Thomas Wu CLA 		no flags Details
screenshot (110.96 KB, image/pjpeg)
2011-09-30 02:43 EDT, Thomas Wu CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wu CLA 2011-09-30 02:41:03 EDT 
Build Identifier: 20110929

There is no Annotation search in RBD.
Annotation search will miss some expected results. The missed ones looks like that, "@Property"; but "@Property{XXX}" will not be missed.

Reproducible: Always

Steps to Reproduce:
1. Import PI from attachment
2. Select the package MainProject/EGLSource/externalTypes. Go to EGL search wizard, set Search string as "*", Search for as "Annotation", Limit To as "All occurrences", Scope as "Selected resources", then click Search button.

Actual results: Some kind of annotations are missed in return results, just like "@Property". But the format of "@Property{XXX}" will not be missed.
Comment 1 Thomas Wu CLA 2011-09-30 02:42:17 EDT 
Created attachment 204342 [details]
PI
Comment 2 Thomas Wu CLA 2011-09-30 02:43:54 EDT 
Created attachment 204343 [details]
screenshot
Comment 3 Zhi Zhu CLA 2011-10-17 04:28:53 EDT 
As for field annotation, whether the following format are identical:

   rname string{@Property};
   rname string{@Property{}};

   From SourceElementParser.handlePropertyBlock, it seems they are different, it treats the second case add valid annotation, but not for first case.
Comment 4 Zhi Zhu CLA 2011-10-17 23:16:00 EDT 
please refer to bug 361199
Comment 5 Zhi Zhu CLA 2011-11-07 19:56:47 EST 
Fix it
Comment 6 Thomas Wu CLA 2011-11-10 20:36:25 EST 
Verified in build 20111110