I installed Kepler on my fairly new mbp running 10.9.1. Initially this worked, but now when it won't open. Clicking on the docked icon shortcut will start eclipse, but the small loading bar gets to slightly past "loading workbench" then the whole app shuts down. Running in the terminal gives me this error:
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.Workbench$55
I read that others were having Java issues with eclipse on mavericks but I'm not sure that is my case, especially since it was previously running. Please help!
Solved this issue by deleting the .metadata folder, forcing eclipse to create a fresh one. Works great now.
Solution
Delete the .metadata directory will make Eclipse run again.
You can find .metadata folder at your workspace directory.
Consequences
All IDE projects structure will be reset. The projects data
will be kept at the file system.
All IDE configuration data will be reset. You'll have to create it again.
FWIW, I found that it was possible to be more surgical. The issue in my case was in the .metadata.plugins\org.eclipse.e4.workbench folder. Clearing that, I lost my UI state, but all of the projects, SVN connections, etc... weren't lost.
Related
I'm using Eclipse Kepler on Windows 7 and recently it became more and more frequent that it takes lots of time when it has to delete files. For example in these contexts:
mvn clean launched from Eclipse
cleaning output folder in case of automatic projects build by Eclipse
deploying a war on a server (deletion of the previous deployment)
I've checked this old question but working in a fresh new workspace has no effect.
I may have a clue: to gain some time I 'help' Eclipse by deleting the files myself with Windows Explorer. Windows often launches a pop-up saying that I need admin right to do that. I just hit Enter (I am admin user) and the files are quickly deleted. If Eclipse had no right to delete the files I would have expected an error, instead it just takes much more time to actually delete the files.
Why could be the cause of that? Knowing that the clue may or may not be relevant.
For the record: no solution has been found to the problem. I got a new desktop with a fresh Win7 image and I don't have the problem, working with the same Eclipse projects.
This would indicate that the problem came from a misconfiguration of the Windows user permission. Sadly, no more details available.
My computer suddenly shut down due to power failure, while I was working on an Android project using my Eclipse Indigo IDE.
Now, if I start Eclipse, only an empty message dialog (see screen shot) appears and Eclipse does not start. What can I do?
(I am using Ubuntu 12.04 LTS)
Mabe Some files found in the .metadata folder of your workspace are damaged, have you tried to launch it by specifying another workspace?
You can manually specify the workspace location on the command line, using the -data command-line argument.
If you don't want to loose a lot of time by trying to fix the problem, you can import your projects into the new workspace, reinstall the plugins that was installed before and everything will be ok. otherwise, you have to take a look on the .log file found in the .metadata folder of your old workspace, analyse the stacktrace and try to understand which plugin is corrupted and delete it manually, and this may take a lot of time, thats why i suggest you the first solution. About the .metadata folder, it is in ~old_workspace/.metadata.
check your filesystems. Maybe something got corrupted when power was lost.
Check my blog post When Eclipse Won't Start and Restoring a Corrupted Workspace in Eclipse
For me, .metadata files were damaged. Since eclipse was not opening at all, changing the workspace was not an option. I deleted following directories, and could start afresh!
.metadata
.buildpath
.project
Hope this helps you as well.
Please note that you will end up loosing all the project settings.
I know my reply is too late. Hope this helps another user.
My Ubuntu in the VMware was shutdown abnormally for some reason. When I logged back in Eclipse would not start. I fixed with the following steps:
removed .lock file in the .metadata folder in the workspace
started eclipse using command line with "-clean" argument
It started fine!!!
I tried to find the corrupted file by removing the files from ~/workspace/.metadata/ one by one until Eclipse could start.
The corrupted file was ~/workspace/.metadata/.plugins/org.eclipse.core.resources/.snap
Once the file was removed Eclipse started normally.
Launched Eclipse Indigo on Windows XP SP3 this morning and noticed it was taking an unusually long time; I have startup plug-ins disabled and my startup time is usually a matter of seconds.
Finally, Eclipse opened with the Welcome screen. I found that a bit odd, considering my default perspective is the Workbench. So I clicked Workbench and the Package Explorer was empty -- all my projects were gone. Also, all of my carefully tuned preferences had been reset.
Fortunately my project files are still intact and I can import them.
I had this happen before on a Mac with Galileo and thought it was just a fluke, but now it's twice that Eclipse has become self-aware.
I had been using Indigo regularly for months and changed nothing in the preferences or .ini during my last session. I do not use an AV and my computer is free of malware.
This is dangerous behavior for a commercial-grade IDE -- any ideas on why this could be happening and what could be done to prevent it in the future?
This happend to me when i accidentally moved the location of my eclipse workspace, if you cleaned up/ resorted files on your computer and moved the eclipse workspace to another directory location the IDE will appear to reset when opened.
Click File -> switch workspace, then find the location of the workspace and your projects will be restored
My Eclipse Indigo regularly resets itself (1-2 times a week). So I always have a backup of .metadata folder and restore it every time.
I tried to switch workspace but Eclipse tells: "An error occured".
Are you sure you didn't make any changes to your workspace?
Eclipse stores your preferences and settings in your workspace folder.
Maybe something happened to that folder.
I am running Eclipse Galileo on Ubuntu 10.04 LTS.
Ubuntu crashed on me today, and after rebooting, I found that Eclipse has completely lost the Java Perspective (it's like the perspective and all associated views never existed) and the .metadata dir in my workspace is empty except for version.ini.
What's up with that?
Why did it happen?
How can I prevent it?
How can I recover from it?
I ran into an issue - When I installed C/C++ and some collaboration projects (not sure which one), I ran into the same issue. I did the eclipse clean and even tried a new workspace. No help. Ran eclipse -debug -console, found that there were some configurations loaded from ~/.eclipse.
Just renamed that directory and restarted and got back all the perspectives!
First I would try to create a new workspace, and see whether there are the missing elements present. If the other workspace is working correctly, then your original workspace got corrupted.
You can import all projects to the new workspace, and try to use it (although this way you may lose the global settings, that are stored in your old workspace, but at least all your projects and project-specific settings are intact).
On the other hand, if the new workspace also does not work, then you could try launching eclipse with the -clean parameter, or uninstalling and reinstalling it.
Question: where does Eclipse store the list of files it opens on startup?
Background: Having installed a plugin into Eclipse which promptly crashed, my Eclipse workspace is in a bit of a state. When started, the building workspace task pauses indefinitely at 20%. Before I uninstall the plugin I want to give it another chance. I have a feeling that the reason Eclipse is pausing is because of a file which was opened when it crashed, which it tries to reopen on startup. If I can stop this file from opening on startup there's a chance I may be able to coax the plugin to behave. The problem is I have no idea where that list of files is persisted between runs of Eclipse.
...a second before I posted this question, I realised I could just delete the file causing the problem (duh). However, the search has frustrated me enough to want to find the answer.
In your workspace the following file contains your workbench information:
.metadata/.plugins/org.eclipse.ui.workbench/workbench.xml
It is possible to delete it (or edit it but that requires some fiddling around I suppose) without breaking your workspace, the file gets regenerated by Eclipse. When you delete it all workbench related settings are lost (ie all editors are closed), but your projects of that workspace stay intact.
Edit: in Eclipse 4.2 the file is
.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi