Eclipse Community Forums: Java Development Tools (JDT) » Not all features available for Java files in referenced jars

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Not all features available for Java files in referenced jars

Show: Today's Messages :: Show Polls :: Message Navigator

Not all features available for Java files in referenced jars [message #663475]

Tue, 05 April 2011 09:12

David Pérez

Messages: 228
Registered: July 2009

Senior Member

I used to use a lot this feature:

Ctrl-F3 for finding methods.
Ctrl-Shift-U for finding occurrences of a method/member/variable inside the current file.

Now in version 3.6.2 and Win32, it doesn't work any more with java files in referenced jars (with attached sources of course). With my own source files, it continues to work.

I think this is a bug, or perhaps a misconfiguration.
Am I right?

David

Report message to a moderator

Re: Not all features available for Java files in referenced jars [message #663488 is a reply to message #663475]

Tue, 05 April 2011 10:26

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

On 05.04.2011 11:12, David PÃ©rez wrote:
> I used to use a lot this feature:
>
> Ctrl-F3 for finding methods.
> Ctrl-Shift-U for finding occurrences of a method/member/variable
> inside the current file.
>
> Now in version 3.6.2 and Win32, it doesn't work any more with java
> files in referenced jars (with attached sources of course). With my
> own source files, it continues to work.
>
> I think this is a bug, or perhaps a misconfiguration.
This can happen if you don't have all required bundles in your workspace
or if there's a bug in the manifest.

Dani
> Am I right?
>
> David

Report message to a moderator

Re: Not all features available for Java files in referenced jars [message #663496 is a reply to message #663488]

Tue, 05 April 2011 11:48

David Pérez

Messages: 228
Registered: July 2009

Senior Member

Thanks Dani, I think you have provided me a right clue. Razz

Because I have modified by hand some MANIFESTs of some 3rd party plugins.
But how can I know, which manifest is wrong?
I know by empirically, that if a manifest is really damaged, the plugin isn't recognized and it doesn't appear in the Plug-ins view.

I have all requiered bundles, because my app works ok.
Maybe some optional dependencies are missing.

David

Dani Megert wrote on Tue, 05 April 2011 06:26

This can happen if you don't have all required bundles in your workspace
or if there's a bug in the manifest.

Dani

Report message to a moderator

Re: Not all features available for Java files in referenced jars [message #663503 is a reply to message #663496]

Tue, 05 April 2011 12:14

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

On 05.04.2011 13:48, David PÃ©rez wrote:
> Thanks Dani, I think you have provided me a right clue. :p Because I
> have modified by hand some MANIFESTs of some 3rd party plugins.
> But how can I know, which manifest is wrong?
It's hard. First' I'd look whether there are build path errors in the
Problems view. Next, you need to verify the dependency chain of the
class where F3 is not working.

Dani
> I know by empirically, that if a manifest is really damaged, the
> plugin isn't recognized and it doesn't appear in the Plug-ins view.
>
> I have all requiered bundles, because my app works ok.
> Maybe some optional dependencies are missing.
>
> David
>
> Dani Megert wrote on Tue, 05 April 2011 06:26
>> This can happen if you don't have all required bundles in your
>> workspace or if there's a bug in the manifest.
>>
>> Dani
>
>

Report message to a moderator

Previous Topic:	Error Code -1073740791 Please Help
Next Topic:	How to open projects (with .project pom.xml) in eclipse ?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 09:24:46 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter