首页 文章

Eclipse的Google插件 - Eclipse无法启动

提问于
浏览
1

我似乎已成功从Eclipse下载了Google插件(v4.2):http://www.gwtproject.org/usingeclipse.html

下载后,我勾选是重启Eclipse以使插件生效 .

它杀死了我当前的Eclipse会话,然后尝试重新启动Eclipse,但只是要求我在启动屏幕(Android Developer Tools黑/绿启动屏幕)之后指定新工作区 .

然后它显示以下错误消息:发生了错误 . 看日志文件

从现在开始我无法打开Eclipse .

到目前为止我已采取的步骤来纠正此问题: - 在提示指定时尝试保留相同的工作区 - 在提示指定时尝试创建新工作区 - 通过命令提示符启动Eclipse并使用-clean - 从.metadata /删除workbench.xmi .plugins / org.eclipse.e4.workbench - 从.metadata / .plugins / org.eclipse.core.resources / file删除.snap不存在

当我找不到解决方案时,我完全重新安装了Eclipse . 重新安装后,我的工作区和过去的项目工作正常 . 在我尝试再次安装Google插件之前,一切都很顺利 . 第二次发生同样的结果

以下是此事件的日志文件的最后一部分:

!ENTRY org.eclipse.e4.ui.workbench 4 0 2014-02-04 16:24:05.633!MESSAGE无法从包'142'创建类'org.eclipse.e4.core.commands.CommandServiceAddon'!STACK 0 org.eclipse.e4.core.di.InjectionException:java.lang.ClassCastException:无法将org.eclipse.core.commands.CommandManager转换为org.eclipse.e4.core.internal中的org.eclipse.core.commands.CommandManager . di.MethodRequestor.execute(MethodRequestor.java:63)位于org.eclipse.e4.core.internal.di.InjectorImpl的org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:861) . 注入(InjectorImpl.java:113)org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:321)org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl . java:255)atg.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:185)atg.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)at org .eclipse.e4.ui.inte rnal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)位于org.eclipse.e4.ui.internal.workbench的org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:49) . swt.E4Application.createE4Workbench(E4Application.java:258)atg.eclipse.ui.internal.Workbench $ 5.run(Workbench.java:557)org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java) :332)org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)位于org.eclipse.ui.internal.ide的org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) . org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)上的application.IDEApplication.start(IDEApplication.java:124) EclipseAppLauncher.java:110)org.eclipse.cor上的org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) e.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)atg.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at at位于org.eclipse.equinox.launcher.Main.invokeFramework的java.lang.reflect.Method.invoke(未知来源)的sun.reflect.DelegatingMethodAccessorImpl.invoke(未知来源)的sun.reflect.NativeMethodAccessorImpl.invoke(未知来源)( Main.java:629)org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)org.eclipse.equinox.launcher.Main.run(Main.java:1438)atg.eclipse.equinox .launcher.Main.main(Main.java:1414)引起:java.lang.ClassCastException:无法在java.lang.Class中将org.eclipse.core.commands.CommandManager转换为org.eclipse.core.commands.CommandManager . 在Org.eclipse.e4.core.internal.contexts.EclipseContext.get(EclipseContext.java:561)的org.eclipse.e4.core.commands.CommandServiceAddon.init(CommandServiceAddon.java:30)中转换(未知来源) sun.reflect.Native位于java.lang.reflect.Method.invoke的sun.reflect.DelegatingMethodAccessorImpl.invoke(未知来源)的sun.reflect.NativeMethodAccessorImpl.invoke(未知来源)上的MethodAccessorImpl.invoke0(Native Method)(未知)来源)org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)... 27更多

!ENTRY org.eclipse.e4.ui.workbench 4 0 2014-02-04 16:24:05.643!MESSAGE无法从包'155创建类'org.eclipse.e4.ui.internal.workbench.addons.CommandProcessingAddon' '!STACK 0 org.eclipse.e4.core.di.InjectionException:无法处理“CommandProcessingAddon.commandService”:没有找到参数“ECommandService”的实际值 . org.eclipse.e4.core.internal.di.InjectorImpl.reportUnresolvedArgument(InjectorImpl.java:396)org.eclipse上的org.eclipse.e4.core.internal.di.InjectorImpl.resolveRequestorArgs(InjectorImpl.java:387)位于org.eclipse.e4.core的org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:321)的.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:102) .internal.di.InjectorImpl.make(InjectorImpl.java:255)org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:185)org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory .createFromBundle(ReflectionContributionFactory.java:105)org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory) .java:49)在org.eclipse.ui的org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:258) . 在org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java)的org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)上的internal.Workbench $ 5.run(Workbench.java:557) :543)org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)位于org.eclipse.equinox的org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) . internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)位于org.eclipse.core.runtime.internal.adaptor的org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) . EclipseAppLauncher.start(EclipseAppLauncher.java:79)位于org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java: 180)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown)来自)org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)的java.lang.reflect.Method.invoke(未知来源)org.eclipse.equinox.launcher.Main.basicRun(Main . java:584)org.eclipse.equinox.launcher.Main.run(Main.java:1438)org.eclipse.equinox.launcher.Main.main(Main.java:1414)

!ENTRY org.eclipse.e4.ui.workbench 4 0 2014-02-04 16:24:05.651!MESSAGE无法从包'158创建类'org.eclipse.e4.ui.workbench.swt.util.BindingProcessingAddon' '!STACK 0 org.eclipse.e4.core.di.InjectionException:无法处理“BindingProcessingAddon.commandService”:没有找到参数“ECommandService”的实际值 . org.eclipse.e4.core.internal.di.InjectorImpl.reportUnresolvedArgument(InjectorImpl.java:396)org.eclipse上的org.eclipse.e4.core.internal.di.InjectorImpl.resolveRequestorArgs(InjectorImpl.java:387)位于org.eclipse.e4.core的org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:321)的.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:102) .internal.di.InjectorImpl.make(InjectorImpl.java:255)org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:185)org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory .createFromBundle(ReflectionContributionFactory.java:105)org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory) .java:49)在org.eclipse.ui的org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:258) . 在org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java)的org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)上的internal.Workbench $ 5.run(Workbench.java:557) :543)org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)at atOrg.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)位于org.eclipse.core的org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) . runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)位于org.eclipse.core.runtime.adaptor.EclipseStarter的org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) . 运行(EclipseStarter.java:180)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 org.eclipse中的org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)中的.Method.invoke(未知来源) .equinox.launcher.Main.run(Main.java:1438)org.eclipse.equinox.launcher.Main.main(Main.java:1414)

!ENTRY org.eclipse.osgi 4 0 2014-02-04 16:24:05.869!MESSAGE应用程序错误!在org.eclipse.e4.ui.internal.workbench.E4Workbench.processHierarchy(E4Workbench . )中堆栈1 java.lang.NullPointerException . 的java:172)在org.eclipse.e4.ui.internal.workbench.E4Workbench.init(E4Workbench.java:118)在org.eclipse.e4.ui.internal.workbench.E4Workbench(E4Workbench.java:69)在 . org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:306)org.eclipse.ui.internal.Workbench $ 5.run(Workbench.java:557)org.eclipse.core位于org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)的org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)中的.databinding.observable.Realm.runWithDefault(Realm.java:332) )org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)org.eclipse的org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) . core.runtime.internal.adaptor.EclipseAppLauncher.runApp位于org.eclipse.core.runtime.adaptor.EclipseStarter.run的org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)中的lication(EclipseAppLauncher.java:110)(EclipseStarter.java: 353)org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)at sun . 在org.eclipse.equinox.launcher的org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)的java.lang.reflect.Method.invoke(未知来源)中反映.DelegatingMethodAccessorImpl.invoke(未知来源) .Main.basicRun(Main.java:584)在org.eclipse.equinox.launcher.Main.run(Main.java:1438)在org.eclipse.equinox.launcher.Main.main(Main.java:1414)

2 回答

  • 0

    以前,我从官方android站点下载ADT SDK包 . 这只给你Eclipse 4.2,而不是4.3 . 因此,我最初必须下载4.2版本的谷歌插件才能与我的Eclipse版本相匹配 - 这就是我收到上述错误的地方 .

    Here was my fix:

    我没有下载ADT SDK包,而是只重新下载了Eclipse,然后分别添加了SDK工具/ ADT插件/平台工具/平台/系统映像 . 从官方的Eclipse站点,我可以下载Eclipse 4.3 .

    然后我下载了谷歌插件4.3 . 它似乎工作正常 . 因此,Eclipse 4.2和Google插件4.2组合似乎存在问题 .

  • 0

    我和你有完全相同的问题,我想我可能会被迫卸载并重新安装整个Eclipse . 我为eclipse 4.2安装了eclipse 4.2的google插件,现在我继续使用长元数据日志获取错误消息 .

    我很惊讶谷歌网站上的常见问题解答没有讨论这个漏洞 . 这真是令人沮丧,我希望在我盲目地相信谷歌插件无故障地工作之前我找到了这个帖子 .

相关问题