Community
Participate
Working Groups
I downloaded the maintenance build of Eclipse (2.1.1). Eclipse couldn't start and here is what I got in the log: !SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 May 01, 2003 10:53:07.584 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.basicRun(Main.java:291) at org.eclipse.core.launcher.Main.run(Main.java:747) at org.eclipse.core.launcher.Main.main(Main.java:583) Caused by: java.lang.RuntimeException: Fatal Error: Unable to locate matching org.eclipse.core.runtime plug-in. at org.eclipse.core.internal.boot.PlatformConfiguration.locateDefaultPlugins (PlatformConfiguration.java:2264) at org.eclipse.core.internal.boot.PlatformConfiguration.<init> (PlatformConfiguration.java:903) at org.eclipse.core.internal.boot.PlatformConfiguration.startup (PlatformConfiguration.java:1368) at org.eclipse.core.internal.boot.InternalBootLoader.initialize (InternalBootLoader.java:582) at org.eclipse.core.internal.boot.InternalBootLoader.startup (InternalBootLoader.java:1006) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:838) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) ... 7 more when I removed my old workspace it booted up fine!
How did you download and install the new version of Eclipse? Did you just download the zip file and then extract it over-top of your already existing install? Moving to Platform/Update for comment.
i installed into a new directory and copied my old workspace accross
Seems the startup picked up the old location We need to investigate
Sonia just got this one too when opening a workspace for the first time with a build n20030702. The workaround was to remove the .config directory. I will attach her .config directory.
Created attachment 5335 [details] <workspace>/.metadata/.config directory (zipped) Sonia Dimitrov's .config directory. This problem is always reproducible if this .config dir is extracted into the workspace metadata area.
*** Bug 39599 has been marked as a duplicate of this bug. ***
*** Bug 41994 has been marked as a duplicate of this bug. ***
In M3 the .config folder has been moved outside the workspace (it is under the eclipse directory, or in some well known location), see bug 37686. Please let us know if this change resolves the problems you were experiencing.
I haven't been able to reproduce this since the initial report because in order to fix it I just deleted the .config folder.
Is there anything else expected to be fixed for this bug? When a new driver is installed, the .config folder needs to be removed as well. Since it is now located inside the eclipse install it gets deleted when you delete your old install.
