Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 205023

Summary:	[search] Search Results provided by an IQueryParticipant are displayed flat
Product:	[Eclipse Project] JDT	Reporter:	Stefan Holzknecht <s.holzknecht>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.kell.r, martinae, Michael_Rennie
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Stefan Holzknecht

2007-10-01 06:05:00 EDT

Build ID: I20070625-1500

Steps To Reproduce:
1. Create and register an IQueryParticipant
2. Perform a search (e.g. for references), your own search participant creates matches that are based on (if applicable fully adaptable - adapting to IResource, IFile, IWorkbenchAdapter, IJavaElement) model objects
3. Note
a) that the elements are not grouped by e.g. resource
b) that a label provider created in your IMatchPresentation is completely ignored
c) there is now way to group your results 

More information:

Comment 1 Martin Aeschlimann

2007-10-02 12:12:12 EDT

If you can adapt to an IResource, then you should report your matches on the IResource.
If this is not the case, it isn't clear to me how we could sort the element in the tree.
I see that it's a bit strange how the contributed label provider is used.

To be honest, this extension point has been around for a long time, with almost no feedback. It's not clear how often it is used. At the moment there are no plans to invest more in this area. Help is welcome.

Comment 2 Michael Rennie

2007-10-29 11:54:42 EDT

Debug uses this to provide a query participant for references to types in Java launch configs. Any results found are just shown as the config icon and name: possibly confusing to novice users that don't know what the config icon is.

It would be cool if there was some way to group the config matches, e.g. have a parent "Launch Configurations" item with all config matches as children...

Comment 3 Markus Keller

2007-10-29 12:22:24 EDT

While I agree that some structure for participant results would be worthwile, I'm not sure whether a global "Launch Configurations" container item would be the best solution. E.g. a Java Application launch configuration could also be shown just inside the enclosing project.

Implementation-wise, we could maybe add support for IWorkbenchAdapter to LevelTreeContentProvider.FastJavaElementProvider.getParent(Object) and somewhere in the label providers.

Comment 4 Michael Rennie

2007-10-29 13:09:50 EDT

I agree it would be better to have the config in the associated project, although we would still need a 'catch-all' for configs that do not have an associated project.

Comment 5 Eclipse Genie

2019-10-06 08:44:25 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. 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.

--
The automated Eclipse Genie.