[news.eclipse.tools.jdt] Re: problems with searching for references

[Rudolf Ziegaus <Rudolf.Ziegaus@xxxxxx>]

Am Fri, 21 Sep 2007 10:57:35 +0200 schrieb Daniel Megert:

> Rudolf Ziegaus wrote:
> 
>>Am Wed, 19 Sep 2007 12:36:35 +0200 schrieb Frederic Fusier:
>>
>>  
>>
>>>Rudolf Ziegaus wrote:
>>>  > Hello Frederic,
>>>    
>>>
>>>>thanks for your reply. No, I did not mean the "File Search" in Eclipse. I
>>>>was talking about using "References" from the context menu. When I choose
>>>>the same working set as I do for my own search, I do get a match for a
>>>>class in "plugin.xml" that I don't get when I use my own search method.
>>>>Maybe Eclipse is doing additionally a search in all found "plugin.xml"
>>>>files?
>>>>
>>>>Rudi
>>>>      
>>>>
>>>You're right, I never noticed that... and it seems to exist since 3.2!
>>>Thanks for the tip :-)
>>>
>>>However, this match is not reported by Search Engine, but by the "PDE Java
>>>Search Participant" which extends the org.eclipse.jdt.ui.queryParticipants
>>>extension point in MANIFEST.MF of org.eclipse.pde.ui plugin.
>>>    
>>>
>>
>>You're welcome;-) 
>>
>>I found the necessary classes. However I have a further question. I'd like
>>to implement this very functionality in my plugin. What's the best way to
>>do it? When I copy the class's source code I have to import many internal
>>packages and I get a "restricted access" message. Is there a better way to
>>implement this functionality? Or can I suppress the warnings? What does
>>this message mean btw?
>>  
>>
> It means you are using internal code which can change anytime.
> 
> Dani
> 
>>Rudi
>>  
>>
Yep, that what I thought. So, it's no good idea to use that code.
What alternatives do I have?
Since I have run into this problem with plugin.xml (that's where an
extension point is referenced) I thought I might as well parse the
plugin.xml for any mention of the class I am looking for.

Is there an "official way" to get the plugin.xml of a project? Of course I
could also look the members of the project and load the plugin.xml from
there. However, if there is an preferred way I would try to stick to that.

Thanks,

Rudi