tags:

views:

1908

answers:

7
+1  A: 

Looks like your mylyn install may be broken try removing the mylyn plugin and see how you get on.

Paul Whelan
Paul (and Daniel), thanks for the tip on Mylyn. I downloaded Eclipse 3.5 Classic that comes without Mylyn and this has made some difference. At least I can continue working now. Cheers.
Damo
+1  A: 

When I had a similar problem, I simply uninstalled the Mylyn/Java integration. I don't use Mylyn, and although I know some people consider it to be the best thing since sliced bread, I've never found it to be anything other than a way to screw my name completion.

Note that you don't want to disable the "Java Proposals (Task-Focused)" that that error message was trying to tell you about. That'll disable name completion as well.

Daniel Martin
+8  A: 
VonC
wow nice answer :)
Paul Whelan
Thanks. It does sound like bug 281871. I've added the codeAssistTimeout and it's all working. Now just need to decide whether to stay with Mylyn or EclipseClassic.
Damo
A: 

I was having the same issue, but my problems started when i upgrade my project from gwt 1.5 to gwt 1.7. I read your comments and i just make two changes. Increase the Xmx to -Xmx768m and unmark Java Proposals (Task-Focused) and mark just Java Proposals. It's being work fine since i did this changes. I hope it can help you.

Eduardo Hitek
A: 

I had the same issue on eclipse 3.5. Upgrading mylyn features resolved it

Thomas
A: 

Mylyn (or its code assist) seems to be rather picky about resources in the build path.

I had the issue and it was caused by binary files which I had accidentally added to the Eclipse built path. That does not cause any compile error or warnings but causes the exception during code completion you mention in your post.

Tobias
A: 

For me it works by doing prefrerences > general > keys > Restore Defaults

Dont know its crazy but thats what finally works after all the googling and trail following.

Regards, Manish

Manish
If you read the question you'll see that it was an Eclipse bug relating to large JAR files. This has now been fixed in the 3.6M6 release of Eclipse.
Damo