Summary: | Can't start 2.0 eclipse | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | LeRoy Kemnitz <lkemnitz> |
Component: | Resources | Assignee: | DJ Houghton <dj.houghton> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | P1 | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
LeRoy Kemnitz
2002-07-05 11:23:14 EDT
Is that the complete log file? Did you write the "... 7 more" or was that part of the stack trace? The reason I ask is because InvocationTargetException is merely a wrapper for another exception, but I can't see that nested exception in the stack trace. Also, what VM are you using? Thanks for taking the time to enter a bug report. This is a mystifying problem, as presumably most others have not experienced this. We've use Win2k for development from the beginning without seeing this. I have since removed all of Eclipse from my machine. I reinstalled 1.0 and got that working back to where it was. I then downloaded the 2.0 again and reinstalled it. Got the same error. The VM, I am not sure. I am using j2sdkee 1.3.1. Tomcat 4.0.3. If that helps. I added nothing to log file. Just copy and paste. The entire log file is too large to post in this box. I will attach it to a message on the board, but the log file ending error is this: rces"> </status> </log-entry> <log-entry date="Fri Jul 05 10:29:04 CDT 2002"> <status code="4" severity="INFO" message="Unable to restore editor - cannot instantiate input element: org.eclipse.ui.part.FileEditorInputFactory" plugin-id="org.eclipse.core.resources"> </status> </log-entry> <log-entry date="Fri Jul 05 10:29:04 CDT 2002"> <status code="4" severity="INFO" message="Unable to restore editor - cannot instantiate input element: org.eclipse.ui.part.FileEditorInputFactory" plugin-id="org.eclipse.core.resources"> </status> </log-entry> </log> !SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 Jul 05, 2002 10:58:10.538 !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.jav a:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.basicRun(Main.java:248) at org.eclipse.core.launcher.Main.run(Main.java:698) at org.eclipse.core.launcher.Main.main(Main.java:534) Caused by: java.lang.NoSuchMethodException: loaderStartup at java.lang.Class.getMethod0(Class.java:1742) at java.lang.Class.getDeclaredMethod(Class.java:1219) at org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBootLoader.jav a:906) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:76 8) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462) ... 7 more Did you install the 2.0 build on top of an older build from the 2.0 stream? We changed from an XML log format to the !ENTRY format about a month ago, and I'm seeing both of these formats in your log file. Also the log should now include the command line arguments from startup, and I don't see those either. It looks like you've got a "mixed" install that contains pieces from multiple builds. Is this possible? I was using the old 1.0 version and installed 2.0 in the same directory. I figured it should overwrite files. The 1.0 I have now is from what I saved from months ago. I will try to just install 2.0 in directory by itself. The 2.0 build works fine now. I will have to keep them seperate on the hard drive. |