| Summary: | [api] make duplicate detection support generic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> | ||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | murphy, robert.elves, steffen.pingel, tomasz.zarna | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 195079, 197513 | ||||||
| Attachments: |
|
||||||
|
Description
Mik Kersten
I think it would be more beneficial in a long run to make AbstractRepositoryQuery generic to all connectors, so they won't have to subclass it. Steffen: do we have anything left here? I've lost track of the recent duplicate detector changes. Consider for 3.0. I have added a new class named AbstractSearchHandler to an internal package in tasks.core. Connectors can extend this class to provide a generic search facility for text by implementing this method: public abstract boolean queryForText(TaskRepository taskRepository, IRepositoryQuery query, TaskData taskData, String text); Search handlers have to be registered by invoking TasksUiPlugin.getDefault().addSearchHandler(). Tasks UI contributes a generic stack trace detector that invokes the appropriate search handler if one exists. We can consider making this API once the search handler interface has been stabilized. Created attachment 100113 [details]
mylyn/context/zip
|