|Re: Removing plug-in dependencies [message #1209732 is a reply to message #1201736]
||Mon, 25 November 2013 17:22
| Gary Worsham
Registered: September 2013
David Wegener wrote on Thu, 21 November 2013 17:20|
Development workspaces should only be used with the Eclipse instance that you use for your development. Runtime workspaces should only be used by launched Eclipse instances. End user workspaces should only be used by Eclipse instances with your stable plugins installed.
I appreciate the clear statement David. So I guess I clearly screwed up, because although I can open both the plug-in development and application development workspaces from the first Eclipse instance, the runtime Eclipse version opens up now and complains that the VM hasn't been set.
I also consistently get the "missing ActionSet" error (see other post in this forum). From my research an "ActionSet" is something like a plug-in pop up menu definition.
The first Eclipse instance often gets stuck with a message at lower right "Initializing Java Tooling" and sometimes it gets stuck at 32% and more recently 41%.
I already completely replaced the Eclipse files, although to be honest I used an "RC" rather than stable version as I was hoping for relief from this missing ActionSet issue.
Either I have botched up my project files such that replacing Eclipse doesn't help, or for some reason my code is actually causing a weird bug in Eclipse to be exposed. While I doubt the latter, it's certainly a non zero possibility.
Any suggestions for how to recover?
[Updated on: Mon, 25 November 2013 17:28]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02850 seconds