| Current text selection does not resolve to a Java element? [message #234308] |
Sat, 12 August 2006 02:07  |
Eclipse User |
|
|
|
Originally posted by: khai.n.situvista.com
I've been using Eclipse for a long time going back to 2.0 and have
recently noticed that I run into this error a lot more now with 3.2.
It used to be that I could browse the Eclipse (compiled) code and
navigate to the declaration of methods, classes, etc... with F3 pretty
consistently, and if no source code is found then a generic page is
displayed showing the signature of the class. With 3.2 I'm frequently
getting "Current text selection does not resolve to a Java element";
this is with F3 (open declaration) or F4(open type hierarchy).
Strangely enough I can always manually go to the class by using the Open
Type dialog, and can fully browse the source for it.
There have been a few mentions of this in the newsgroup but nothing
definitive have been given to 'solve it once and for all'.
In short, what is the actual requirement that must be met in order to
browse through a particular compiled class and have the full use of F3
and F4?
What if I want this for the entire Eclipse codebase?
Thanks for any answers!
-- Khai --
|
|
|
|
| Re: Current text selection does not resolve to a Java element? [message #234604 is a reply to message #234494] |
Thu, 17 August 2006 02:46  |
| Eclipse User |
|
|
|
Originally posted by: khai.n.situvista.com
Hey thanks, I don't know why I didn't think of that... Duh!!! :-P
-- Khai --
Daniel Megert wrote:
> Khai M Nguyen wrote:
>
>> I've been using Eclipse for a long time going back to 2.0 and have
>> recently noticed that I run into this error a lot more now with 3.2.
>>
>> It used to be that I could browse the Eclipse (compiled) code and
>> navigate to the declaration of methods, classes, etc... with F3 pretty
>> consistently, and if no source code is found then a generic page is
>> displayed showing the signature of the class. With 3.2 I'm frequently
>> getting "Current text selection does not resolve to a Java element";
>> this is with F3 (open declaration) or F4(open type hierarchy).
>>
>> Strangely enough I can always manually go to the class by using the
>> Open Type dialog, and can fully browse the source for it.
>>
>> There have been a few mentions of this in the newsgroup but nothing
>> definitive have been given to 'solve it once and for all'.
>>
>> In short, what is the actual requirement that must be met in order to
>> browse through a particular compiled class and have the full use of F3
>> and F4?
>
> To get this the best way is to import all the required plug-ins either
> as 'Binary projects' or as 'Binary projects with linked content'.
>
>>
>> What if I want this for the entire Eclipse codebase?
>
> Then do the above for the entire content. In this case I suggest to use
> 'Binary projects with linked content'.
>
> Dani
>
>>
>>
>> Thanks for any answers!
>>
>> -- Khai --
>>
|
|
|
Powered by
FUDForum. Page generated in 0.04186 seconds
] 
Search
Help
Register
Login
Home
