Bug 301247 - org.eclipse.search depends on .core.resources, barring use in RCP
Summary: org.eclipse.search depends on .core.resources, barring use in RCP
Status: CLOSED DUPLICATE of bug 77424
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Search (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Search-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-29 08:52 EST by Stijn van Drongelen CLA
Modified: 2010-02-01 05:51 EST (History)
2 users (show)

See Also:

Attachments
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 Stijn van Drongelen CLA 2010-01-29 08:52:52 EST 
Build Identifier: Build id: 20090920-1017

The Search plugin of Eclipse can't be used in RCP applications. For the Replace functionality, the plugin depends on o.e.ltk.core.refactoring and .ui.refactoring, which both depend on o.e.core.resources.

Furthermore, the Search plugin depends directly on o.e.c.r.

Since o.e.core.resources isn't considered part of RCP, o.e.search can't be used in RCP projects either.

I understand it's not easy to decouple Replace from Find, but it would be useful if the component could be used in applications which are very unlike IDEs or text editors.

Reproducible: Always
Comment 1 Dani Megert CLA 2010-02-01 05:51:31 EST 
The problem is not the separation of search/replace but rather the search framework from the file/text search which is completely resource based.

>Since o.e.core.resources isn't considered part of RCP, o.e.search can't be used
>in RCP projects either.
This statement is incorrect: RCP simply defines a set of bundles but of course you can add any additional bundles, e.g. org.eclipse.core.resources, if that fits your needs.

*** This bug has been marked as a duplicate of bug 77424 ***