Weird thing this morning, started Eclipse, like usual, using my PortableProgram frontloader and I got an error from the past, an error, I happen to know made me reinstall eclipse from a backup cause I couldnt find the real cause. The error was that eclipse cannot be started and I had a log of the error in the file:
WorkspaceLocation/.metadata/.log
Looking at this file, I found LOOOOOOOOADS of errors, all relating to not being able to find the plugin information it needs to start, which was blocking Eclipse from functioning properly. Here is a snippet if you recognise something similar, maybe this solution will help you as well as it helped me.
[chris@chris eclipse]$ cat /media/Shadows/projects/work/bluemedia/workspace/.metadata/.log
!SESSION 2007-06-21 01:00:48.101 ———————————————–
eclipse.buildId=M20070212-1330
java.version=1.6.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=es_ES
Command-line arguments: -os linux -ws gtk -arch x86This is a continuation of log file /media/Shadows/projects/work/bluemedia/workspace/.metadata/.bak_0.log
Created Time: 2007-06-21 01:01:21.205!ENTRY org.eclipse.osgi 4 0 2007-06-21 01:01:21.206
!MESSAGE Application error
!STACK 1
java.lang.NoClassDefFoundError: org/eclipse/core/resources/IContainer
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
ETC, ETC, ETC, ETC, ETC……………..!ENTRY org.eclipse.osgi 2 0 2007-06-21 01:01:22.332
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-21 01:01:22.332
!MESSAGE Bundle update@plugins/org.eclipse.birt.report.data.oda.jdbc_2.2.0.v20070531/ was not resolved.
!SUBENTRY 2 org.eclipse.birt.report.data.oda.jdbc 2 0 2007-06-21 01:01:22.332
!MESSAGE Missing required bundle org.eclipse.datatools.connectivity.oda_[3.1.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-06-21 01:01:22.333
!MESSAGE Bundle update@plugins/org.eclipse.birt.report.data.oda.jdbc.ui_2.2.0.v20070531.jar was not resolved.
!SUBENTRY 2 org.eclipse.birt.report.data.oda.jdbc.ui 2 0 2007-06-21 01:01:22.333
!MESSAGE Missing required bundle org.eclipse.datatools.connectivity.oda.design.ui_[3.0.4,4.0.0).
ETC, ETC, ETC, ETC……..
So, you can imagine what I am thinking, this worked perfectly 5 hours ago, I closed Eclipse, now it doesnt work.
Well, the solution in the end was quite simple, what I did was I deleted the directory
WorkspaceLocation/configuration/.settings
and Re-ran eclipse, I was confronted with the choose a workspace dialog, I selected a workspace and it opened without any of those problems.
I am not entirely sure of why this is caused, but at least I know a way to stop and prevent it!!!
UPDATE #1:
Even though now you can run Eclipse, you still cannot open the affected workspace. I have found that there is actually a relationship between this crash and a file called a .snap file that is contained inside the workspace directory you are trying to open. If you delete the file
WorkspaceLocation/.metadata/org.eclipse.core.resources/.snap
(if it exists)and attempt to open the workspace again, it’ll work, UNFORTUNATELY, all your projects are now missing and I am sure deleting that file will erase ALL your project settings (it has to me in this instance). But if you cannot even open the workspace, it might be easier for you to recreate them than to create a brand new workspace, it’s up to you which solution you use, I’ll have to investigate this further the next time it happens.
Ciao for now!
#1 by Marc Limotte on March 20, 2009 - 2:48 am
Quote
I see this is an old post. But a helpful one.
I had no “WorkspaceLocation/configuration/.settings” (maybe no moved in latest version of Eclipse). But removing “WorkspaceLocation/.metadata/org.eclipse.core.resources/.snap” resolved the problem. As you point out, it leaves you with a blank workspace, but the situation isn’t totally bleak. You can import your existing projects and your project specific settings are restored.
Thanks for the post.
#2 by marco tulio corona pacheco on July 20, 2009 - 7:24 am
Quote
wuauuuu!!
Thanks guys !!
it worked for me.
thanks a lot again
From México
#3 by Ricardo Assing on August 7, 2009 - 5:00 pm
Quote
Worked like a charm.. Saved me from hours of stress. Thanks.
#4 by Sue Zzz on October 16, 2009 - 2:54 am
Quote
Thanks a lot. It works for me.
#5 by Javier on January 19, 2010 - 12:14 am
Quote
About your solution, thanks, It was great. Only one thing, if you delete .snap file, and re-start the eclipse (I am using Ganymede version) using the same workspace, Eclipse is ready to rebuild the workspace without do anything else.
#6 by chris on January 19, 2010 - 12:25 am
Quote
javier: how is that a problem though, perhaps I didnt understand your post?
#7 by Prasad on August 3, 2010 - 2:09 pm
Quote
It happens with me too and I just renamed my workspace to someother name and tried to open the eclipse it works fine for me.
I’m not sure why this happens. Need to investigate why this happens.
#8 by Prasad on August 3, 2010 - 2:12 pm
Quote
It happens with me too and I just renamed my workspace to someother name and tried to open the eclipse it works fine for me.
I’m not sure why this happens. Need to investigate why this happens.
Only thing we have to do here is again need to create the projects here from your backup folder.
#9 by chris on August 3, 2010 - 2:47 pm
Quote
ah I never tried that, good solution! thanks prasad!!