Community
Participate
Working Groups
!SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 lis 04, 2003 11:11:16.546 !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:299) at org.eclipse.core.launcher.Main.run(Main.java:765) at org.eclipse.core.launcher.Main.main(Main.java:599) Caused by: java.lang.reflect.InvocationTargetException at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:861) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) ... 7 more Caused by: java.lang.AbstractMethodError at org.eclipse.ui.internal.commands.CommandManager.readRegistry (CommandManager.java:763) at org.eclipse.ui.internal.commands.CommandManager.<init> (CommandManager.java:198) at org.eclipse.ui.internal.commands.CommandManager.getInstance (CommandManager.java:67) at org.eclipse.ui.internal.Workbench.initializeCommandsAndContexts (Workbench.java:1021) at org.eclipse.ui.internal.Workbench.init(Workbench.java:1710) at org.eclipse.ui.internal.Workbench.run(Workbench.java:2318) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:858) ... 8 more
Created attachment 6641 [details] Metadata In logs i find report, that luncher cannot read registry, so in attachment i send metadata catalog.
What VM are you running on?
java version "1.4.0_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_03-b04) Java HotSpot(TM) Client VM (build 1.4.0_03-b04, mixed mode)
This is a bug in Sun 1.4.0 VM. Please use a newer Sun JDK/JRE (>= 1.4.1). See duplicate for more details. Last question: which Eclipse 3.0 build are you using? *** This bug has been marked as a duplicate of 44687 ***