Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366306 - [Improvement] Context sensitive search providers should be able to show their results in the search console
Summary: [Improvement] Context sensitive search providers should be able to show their...
Status: CLOSED WONTFIX
Alias: None
Product: e4
Classification: Eclipse Project
Component: Search (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-10 10:01 EST by Danail Branekov CLA
Modified: 2019-09-04 03:11 EDT (History)
4 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 Danail Branekov CLA 2011-12-10 10:01:10 EST 
Searches done directly on an element (e.g. search for references via context menu) should be able to make their way into the Search Console. Besides the very results, relevant search parameters should be probably also set.

For example, if one searches for references of class "MyClass" in the workspace and the result is to be shown in the console, then the parameters should be set to 
 - Native console parameters UI:
                - Search for: Java
                - Search in: N/A
- Java search specific UI
                - Search For: Type
                - Limit to: References
                - Search In: Sources + Required projects + Application libraries
                - Scope: Workspace
Showing only search results (without the very parameters) in this scenario would be probably pretty confusing to users
Comment 1 Lars Vogel CLA 2019-09-04 03:11:59 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--