代码之家  ›  专栏  ›  技术社区  ›  Ian Carpenter

Eclipse启动时出错,现在我的包资源管理器为空

  •  4
  • Ian Carpenter  · 技术社区  · 15 年前

    我目前正在学习Java,它结合了头一本Java图书和Eclipse。直到今晚一切都很顺利!

    当我今晚启动Eclipse时,我看到了一条错误消息,我没有注意到(我知道!我知道!)并确认之后,项目资源管理器是空的,它曾经包含我的头第一个项目!

    在快速“谷歌”之后,我找到了workspace.metadata.log,错误如下所示。

    我使用的Eclipse版本是:20100218-1602,我使用的唯一插件是egit。

    任何帮助都将不胜感激。

    !SESSION 2010-06-08 19:24:33.841 -----------------------------------------------
    eclipse.buildId=unknown
    java.version=1.5.0_22
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
    Framework arguments:  -product org.eclipse.epp.package.java.product
    Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.java.product
    
    !ENTRY org.eclipse.ui.workbench 4 2 2010-06-08 19:24:36.475
    !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
    !STACK 1
    org.eclipse.ui.WorkbenchException: Content is not allowed in prolog.
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:121)
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:64)
        at org.eclipse.ui.internal.Workbench$49.run(Workbench.java:1895)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1890)
        at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)
        at org.eclipse.ui.application.WorkbenchAdvisor$1.run(WorkbenchAdvisor.java:781)
    Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:94)
        ... 6 more
    !SUBENTRY 1 org.eclipse.ui 4 0 2010-06-08 19:24:36.475
    !MESSAGE Content is not allowed in prolog.
    !STACK 0
    org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:94)
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:64)
        at org.eclipse.ui.internal.Workbench$49.run(Workbench.java:1895)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1890)
        at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)
        at org.eclipse.ui.application.WorkbenchAdvisor$1.run(WorkbenchAdvisor.java:781)
    !SUBENTRY 1 org.eclipse.ui 4 0 2010-06-08 19:24:36.475
    !MESSAGE Content is not allowed in prolog.
    !STACK 0
    org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:94)
        at org.eclipse.ui.XMLMemento.createReadRoot(XMLMemento.java:64)
        at org.eclipse.ui.internal.Workbench$49.run(Workbench.java:1895)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1890)
        at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)
        at org.eclipse.ui.application.WorkbenchAdvisor$1.run(WorkbenchAdvisor.java:781)
    
    !ENTRY org.eclipse.jdt.ui 4 10001 2010-06-08 19:24:41.442
    !MESSAGE Internal Error
    !STACK 1
    org.eclipse.jdt.internal.ui.JavaUIException: Problems reading information from XML 'OpenTypeHistory.xml'
        at org.eclipse.jdt.internal.corext.util.History.createException(History.java:70)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:257)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:166)
        at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.<init>(OpenTypeHistory.java:199)
        at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.getInstance(OpenTypeHistory.java:185)
        at org.eclipse.jdt.internal.ui.JavaPlugin.initializeAfterLoad(JavaPlugin.java:381)
        at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:255)
        ... 6 more
    !SUBENTRY 1 org.eclipse.jdt.ui 4 4 2010-06-08 19:24:41.442
    !MESSAGE Problems reading information from XML 'OpenTypeHistory.xml'
    !STACK 0
    org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:255)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:166)
        at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.<init>(OpenTypeHistory.java:199)
        at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.getInstance(OpenTypeHistory.java:185)
        at org.eclipse.jdt.internal.ui.JavaPlugin.initializeAfterLoad(JavaPlugin.java:381)
        at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    
    !ENTRY org.eclipse.jdt.ui 4 10001 2010-06-08 19:24:50.435
    !MESSAGE Internal Error
    !STACK 1
    org.eclipse.jdt.internal.ui.JavaUIException: Problems reading information from XML 'QualifiedTypeNameHistory.xml'
        at org.eclipse.jdt.internal.corext.util.History.createException(History.java:70)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:257)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:166)
        at org.eclipse.jdt.internal.corext.util.QualifiedTypeNameHistory.<init>(QualifiedTypeNameHistory.java:33)
        at org.eclipse.jdt.internal.corext.util.QualifiedTypeNameHistory.getDefault(QualifiedTypeNameHistory.java:26)
        at org.eclipse.jdt.internal.ui.JavaPlugin.stop(JavaPlugin.java:602)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:843)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:836)
        at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:474)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:546)
        at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1098)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:593)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:261)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:216)
        at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:266)
        at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:685)
        at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:583)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:409)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
        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:592)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:255)
        ... 25 more
    !SUBENTRY 1 org.eclipse.jdt.ui 4 4 2010-06-08 19:24:50.435
    !MESSAGE Problems reading information from XML 'QualifiedTypeNameHistory.xml'
    !STACK 0
    org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:255)
        at org.eclipse.jdt.internal.corext.util.History.load(History.java:166)
        at org.eclipse.jdt.internal.corext.util.QualifiedTypeNameHistory.<init>(QualifiedTypeNameHistory.java:33)
        at org.eclipse.jdt.internal.corext.util.QualifiedTypeNameHistory.getDefault(QualifiedTypeNameHistory.java:26)
        at org.eclipse.jdt.internal.ui.JavaPlugin.stop(JavaPlugin.java:602)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:843)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:836)
        at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:474)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:546)
        at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1098)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:593)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:261)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:216)
        at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:266)
        at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:685)
        at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:583)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:409)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
        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:592)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    
    4 回复  |  直到 11 年前
        1
  •  3
  •   BlairHippo    15 年前

    啊,日蚀错误。没有什么能比得上你最重要的工具了,把它拿出来,上帝知道用它来启动你的一天有多恐怖…

    你见过吗? this page? 当我自己诊断Eclipse错误时,我的策略是谷歌搜索“Eclipse”以及我能找到的任何错误消息。上面的链接来自于谷歌搜索:

    "Problems reading information from XML 'OpenTypeHistory.xml'" eclipse

    虽然我确信你现在已经弄清楚了,但肯定有一个文件在某个地方被破坏了。希望这有帮助,我希望你能在不损失任何工作的情况下解决问题。

        2
  •  6
  •   prashant    15 年前

    上次你正确关闭Eclipse了吗?我将继续创建一个新的工作区,然后在其中导入我的项目文件。最好把时间花在学习上,而不是弄清楚Eclipse出了什么问题:—)

        3
  •  1
  •   Dax    12 年前

    当然有些文件在Eclipse中被破坏了。甚至我也尝试过Prashant(创建新工作区)给出的解决方案,但不幸的是,这对我来说并不适用。我已经有了日食的副本。所以我重新安装了Eclipse,现在一切正常。最好重新安装Eclipse。

        4
  •  1
  •   larrywhenson    11 年前

    我在彻底关机后也遇到了同样的问题。从我的工作区备份中复制.metadata目录后,项目将再次出现。