Summary: | Switching from jdk1.3.1 to jdk1.4.1 leaves me without CVS support | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Cristian Popescu <cristian.popescu> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | major | ||
Priority: | P3 | CC: | Olivier_Thomann |
Version: | 2.0.1 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Cristian Popescu
2002-10-25 09:10:56 EDT
There have been several problems of this type reported on the newsgroup (you can do a search for VerifyError to see the different threads about the subject). This does not seem to be a CVS issue so I'm forwarding it to the JDT core for comment. Which version of Eclipse are you using? Would it be possible that you have a xerces jar file somewhere on your classpath which might interfere with Eclipse one? Please check your extdirs directory. It might be related to a conflict in the SAX version. The xerces.jar on the classpath should be your problem. Hre is a copy of a message posted on the Eclipse newsgroup about a week ago: I have been working on a project for work the last two weeks and it is nearing completion, but I have a problem. I added a view to my plugin project (very simple view), updated the plugin.xml file, hit the go button (to launch in another workspace for testing) and almost instantly I recieved a java.lang.VerifyError exception. I though, hum, goofed something in the plugin.xml... I checked it, everything looked fine. I reverted to my prior CVS copy (that was committed one day ago), hit the run button again, same error. I then though, hum, something in my .java file of the new view? I deleted it. Hit run, same error. After hours of trying to figure it out, I made a copy of my project outside the workspace tree, deleted the project, checked it back out of CVS (no new code was ever committed to CVS), recomplied, hit the go button and the exact error again. Can anyone help me with this error? I have included the whole error below. Thank you, Jeremy Cowgar jc@cowgar.com ------------------------ java.lang.VerifyError: (class: org/eclipse/core/internal/plugins/PluginParser, method: initializeParser signature: ()V) Incompatible object argument for function call at org.eclipse.core.internal.plugins.RegistryLoader.processManifestFile(RegistryLoader.java:89) at org.eclipse.core.internal.plugins.RegistryLoader.processPluginPathFile(RegistryLoader.java:136) at org.eclipse.core.internal.plugins.RegistryLoader.processPluginPathEntry(RegistryLoader.java:127) at org.eclipse.core.internal.plugins.RegistryLoader.processManifestFiles(RegistryLoader.java:104) at org.eclipse.core.internal.plugins.RegistryLoader.parseRegistry(RegistryLoader.java:63) at org.eclipse.core.internal.plugins.RegistryLoader.parseRegistry(RegistryLoader.java:71) at org.eclipse.core.internal.runtime.InternalPlatform.parsePlugins(InternalPlatform.java:742) at org.eclipse.core.internal.runtime.InternalPlatform.loadRegistry(InternalPlatform.java:686) at org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(InternalPlatform.java:562) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBootLoader.java:909) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:768) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:432) at EclipseRuntimeLauncher.main(EclipseRuntimeLauncher.java:24) Exception in thread "main" And its solution: Fixed! when xereces.jar is in the classpath, the error occurs. When xereces.jar is not in the classpath, all works as normal (except my JasperReports which uses xereces.jar... now what to do?) Jeremy Cowgar jc@cowgar.com Hopefully you have exactly the same issue. Please put a note in this PR if you fix your problem. It was indeed the problem of xerces.jar, so now I run eclipse with jre1.3.1, and set-up the project to build with jdk1.4.1 (I've created a batch file in wich I set the path to jre1.3.1's java as the first entry, and then launch eclipse.exe). Thanks again, Cristian Closing. Closing. Eclipse CP issue |