On Jan 14, 11:41 am, Blessed Geek <[email protected]> wrote: > Is any of your resources sitting in a foreign file system like smb, > ntfs or nfs?
No, all of my resources are local. They are attached to a SVN repository, but the subversion plugin does not communicate with the repository at that time. > > And do you have many projects mounted like I do? I had the same > problem and I had to kill/restart the connector process to the foreign > file system, whenever this happens. I would notice thrashing going own > in the connection and eclipse got stuck. Again no. It is the only project in this workspace (just a test project). > [...] > Perhaps, you could turn autobuild off everytime you exit eclipse so > that it when eclipse is started, it would not autobuild - and turn it > back on when eclipse startup has quieted down. That was a hint in the right direction, I think. I have disabled the google plugin, closed the project, reactivated the plugin and after a startup and some time for eclipse to organize itself, I opened the project. That did the trick. In my opinion this is not a very elegant solution, but it works for me so far. Thank you very much for your help! Greetings, Peter
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
