Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353114 - Model search: search stops at first match
Summary: Model search: search stops at first match
Status: CLOSED FIXED
Alias: None
Product: CBI
Classification: Technology
Component: CBI p2 Repository Aggregator (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-26 10:12 EDT by Miles Daffin CLA
Modified: 2016-09-16 15:51 EDT (History)
3 users (show)

See Also:


Attachments
Model for demoing find bug (1.72 KB, text/plain)
2011-11-14 09:59 EST, Miles Daffin CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Daffin CLA 2011-07-26 10:12:48 EDT
Currently the search stops at the first match it finds in the model and will not go beyond this when there are other matches. If you select a point beyond the first match and try again, hoping to find the next match from that point, the search again finds the first match in the model.
Comment 1 Miles Daffin CLA 2011-11-14 09:59:00 EST
Created attachment 206949 [details]
Model for demoing find bug

1. Load this model
2. Find IUs starting with 'org'
3. The find will open Categories node in the GRECLIPSE repo in the repo browser and cycle through the categories there because their IU names all start with 'org'. However it will *not* find anything else in the model.
4. Open the Features node in the same repo.
5. Search again for 'org. This time the find will cycle through feature IUs in the feature node as well as category nodes from the open Category node above. 
6. Close the category node and search again for 'org'. After a few clicks the category node opens again and the search cycles through matching IUs there before continuing over matches in the features node.
7. Close the features node and run the find again. Search will only find matches in the categories node. The feature node will not be opened.
Comment 2 Miles Daffin CLA 2011-11-14 10:02:04 EST
Updating to critical since this is getting in the way somewhat.
Comment 3 Thomas Hallgren CLA 2011-11-14 10:37:02 EST
Do you consider a minor glitch in the 'find' function as 'critical'? Here's a definition of severity levels that I've found useful in the past.

trivial
Cosmetic problem like misspelled words or misaligned text

minor
Minor loss of function, or other problem where easy workaround is present

normal
Common loss of function.

major
Major loss of function.

critical
Crashes, loss of data, consumes all resources.

blocker
Blocks all further progress.
Comment 4 Thomas Hallgren CLA 2011-11-14 10:39:43 EST
The WTP project has a pretty good and elaborate explanation here: http://wiki.eclipse.org/WTP/Conventions_of_bug_priority_and_severity
Comment 5 Thomas Hallgren CLA 2011-11-24 11:09:05 EST
Fixed on master with commit http://git.eclipse.org/c/b3/b3.git/commit/?id=8174fdf0b2f3666825d925f444bf5342e70ff6d8
Comment 6 Miles Daffin CLA 2011-11-30 14:54:16 EST
Tested  b3 Aggregator Editor (Incubation) 0.2.0.v20111124-1605	org.eclipse.b3.aggregator.editor.feature.feature.group. Find works now. Closing. Thanks.
Comment 7 David Williams CLA 2016-09-16 15:51:38 EDT
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.
Made no changes to assignee's for closed bugs, even though some were old inbox.]