Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 20687 - Debian (Sid) eclipse F3 doesn't start
Summary: Debian (Sid) eclipse F3 doesn't start
Status: RESOLVED DUPLICATE of bug 19252
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux-GTK
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: DJ Houghton CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-19 16:55 EDT by Grzegorz Gierlik CLA
Modified: 2002-06-26 05:52 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grzegorz Gierlik CLA 2002-06-19 16:55:02 EDT
Debian (Sid) Eclipse F3 doesn't start, both GTK and Motif version.
I installed in /opt/eclipse and ran ldconfig.
Previous version F2 and M3 I tried only GTK) work fine.

Now I get splash screen, next something like window appeared for a moment
and I got next dialog window "Problems during startup. Check the '.log' 
file..."
In .log file I found:
!SESSION 
----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 cze 19, 2002 22:42:33.819
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.ExceptionInInitializerError
        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:716)
        at 
org.eclipse.core.internal.runtime.InternalPlatform.loadRegistry(InternalPlatform.java:665)


        at 
org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(InternalPlatform.java:561)
        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.internal.boot.InternalBootLoader.startup(InternalBootLoader.java:873)
        at 
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:732)
        at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
        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:248)
at org.eclipse.core.launcher.Main.run(Main.java:697)
        at org.eclipse.core.launcher.Main.main(Main.java:530)
Caused by: java.lang.ClassCastException: 
org.apache.xerces.parsers.StandardParserConfiguration
        at org.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:95)
        at 
org.eclipse.core.internal.plugins.PluginParser.initializeParser(PluginParser.java:78)
        at 
org.eclipse.core.internal.plugins.PluginParser.<clinit>(PluginParser.java:43)
        ... 23 more

The same message with motif version.
JDK 1.4 from Sun.
Nothig were changed except Eclipse version from F2 to F3 (by removing 
previous).

I tried run it with -ws gtk option and -Djava.library.path=path do .so files
(I found this on eclipse.tools newsgroup).
Comment 1 John Arthorne CLA 2002-06-19 17:39:46 EDT
A new implementation of xerces was shipped with F3.  Is it possible you have an 
incompatible version of xerces somewhere on your classpath?  There have also 
been reports of Sun J2SE 1.4 including an incompatible version of xerces.  What 
VM are you using?
Comment 2 Grzegorz Gierlik CLA 2002-06-20 03:09:14 EDT
I forgot. I use KDE 2.0.
Comment 3 Grzegorz Gierlik CLA 2002-06-21 03:47:29 EDT
The same I got with Gnome and Window Maker.
And the same with F2 when I tried to return to it...
So probably my last Debian upgrade spoilt some libararies.
Comment 4 John Arthorne CLA 2002-06-25 14:31:45 EDT
Please followup again if you find out what caused this.  The answer might be 
helpful to others in this situation...
Comment 5 Grzegorz Gierlik CLA 2002-06-26 05:52:16 EDT
From bug #19252:

------- Additional Comments From Timothy Folks 2002-06-17 04:01 -------

The problem is 
that, contrary to what Sun's JAXP pluggability FAQ tells you,
must place both xercesImpl.jar 
and xmlParserAPIs.jar into the jre\lib\endorsed
directory. This is not an Eclipse bug, but a 
Sun documentation bug.

--
I have forgotten about copying xerces libraries into jre/ext 
directory.
When I removed its from /jre/ext directory Eclipse runs without problems.

*** This bug has been marked as a duplicate of 19252 ***