[JBoss JIRA] (JBIDE-20311) Cannot Show in Web Browser any OpenShift application
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20311?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20311:
----------------------------------------
Labels: respin-a respin-b (was: respin-a)
> Cannot Show in Web Browser any OpenShift application
> ----------------------------------------------------
>
> Key: JBIDE-20311
> URL: https://issues.jboss.org/browse/JBIDE-20311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-a, respin-b
> Fix For: 4.3.0.Beta2
>
>
> Trying to Show in - Web Browser OpenShift applications causes error in tooling. It is similar error for all use cases showing in browser.
> Error for Show in - Web Browser opened via context menu of a project:
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.openBrowser(OpenInWebBrowserHandler.java:87)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.access$0(OpenInWebBrowserHandler.java:80)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler$1.updateUI(OpenInWebBrowserHandler.java:67)
> at org.jboss.tools.openshift.internal.common.ui.job.UIUpdatingJob$1$1.runInUIThread(UIUpdatingJob.java:36)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> And error for Show in - Web Browser opened from context menu of a routing:
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.openBrowser(OpenInWebBrowserHandler.java:87)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.execute(OpenInWebBrowserHandler.java:43)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> Show In - Web Browser via context menu of an application (v2).
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.express.internal.ui.command.OpenInWebBrowserHandler.execute(OpenInWebBrowserHandler.java:38)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20375) Investigate possibility of reading Download Manager data from a REST service instead of YAML
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20375?page=com.atlassian.jira.plugi... ]
David Hladky commented on JBIDE-20375:
--------------------------------------
The rest service has following address: [https://developers.redhat.com/download-manager/rest/available]. At this moment it is possible to narrow search to a specific product by adding a subdirectory (using a product code). For example [https://developers.redhat.com/download-manager/rest/available/eap].
For the web pages every download is important, but I think it makes sense to filter the downloads for the Eclipse plugin to contain only relevant files. [~rob.stryker], I think you know more about how they are filtered in Yaml. We would need to add this information to DM as well and extend the rest service to enable filtering by this information. I think it is fairly easy thing.
Also at this moment the rest service returns information about the terms and conditions model (the requirement of the user credentials is driven by it), but I think it makes sense to add a flag for you, that will tell you, if the specific file requires authentication or not so you do not need to calculate it from the TC model yourself.
> Investigate possibility of reading Download Manager data from a REST service instead of YAML
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20375
> URL: https://issues.jboss.org/browse/JBIDE-20375
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: David Hladky
>
> Download Manager has a rest service, that contains information about all downloads on developers.redhat.com web page (and also many projects on www.jboss.org product pages). In the next year it will start also showing content from ITs unified Download Manager so the number of downloads it describes will become even higher.
> Because our productization team (I think [~pmuir], [~cobrien_redhat]), has to fill the information about existing downloads to many places (from what I know they must upload it to access.cdn, they must enter information about it to Download Manager, they must mention it in Yaml files, they must upload it to customer portal, some of those to Unified download manager as well...). In my opinion it is quite tedious process that we have a chance to make less complicated.
> Download manager will be a source for the product web pages and as it already contains most of the necessary information [~wesbos] is working on it an he is fairly close to this goal.
> And if we have enough information about that why not use it and replicate the information in a different process?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20375) Investigate possibility of reading Download Manager data from a REST service instead of YAML
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20375?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20375:
---------------------------------------------
I do not see the value in tying us to a webservice which are limited to a very specific subset of product downloads.
stacks.yml contains much more info than what download manager provides.
not following what this would give us ?
> Investigate possibility of reading Download Manager data from a REST service instead of YAML
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20375
> URL: https://issues.jboss.org/browse/JBIDE-20375
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: David Hladky
>
> Download Manager has a rest service, that contains information about all downloads on developers.redhat.com web page (and also many projects on www.jboss.org product pages). In the next year it will start also showing content from ITs unified Download Manager so the number of downloads it describes will become even higher.
> Because our productization team (I think [~pmuir], [~cobrien_redhat]), has to fill the information about existing downloads to many places (from what I know they must upload it to access.cdn, they must enter information about it to Download Manager, they must mention it in Yaml files, they must upload it to customer portal, some of those to Unified download manager as well...). In my opinion it is quite tedious process that we have a chance to make less complicated.
> Download manager will be a source for the product web pages and as it already contains most of the necessary information [~wesbos] is working on it an he is fairly close to this goal.
> And if we have enough information about that why not use it and replicate the information in a different process?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20375) Investigate possibility of reading Download Manager data from a REST service instead of YAML
by David Hladky (JIRA)
David Hladky created JBIDE-20375:
------------------------------------
Summary: Investigate possibility of reading Download Manager data from a REST service instead of YAML
Key: JBIDE-20375
URL: https://issues.jboss.org/browse/JBIDE-20375
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: David Hladky
Download Manager has a rest service, that contains information about all downloads on developers.redhat.com web page (and also many projects on www.jboss.org product pages). In the next year it will start also showing content from ITs unified Download Manager so the number of downloads it describes will become even higher.
Because our productization team (I think [~pmuir], [~cobrien_redhat]), has to fill the information about existing downloads to many places (from what I know they must upload it to access.cdn, they must enter information about it to Download Manager, they must mention it in Yaml files, they must upload it to customer portal, some of those to Unified download manager as well...). In my opinion it is quite tedious process that we have a chance to make less complicated.
Download manager will be a source for the product web pages and as it already contains most of the necessary information [~wesbos] is working on it an he is fairly close to this goal.
And if we have enough information about that why not use it and replicate the information in a different process?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20318) [FeedHenry] Unable to copy fhconfig.json template to project
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20318?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-20318.
------------------------------
Verified in JBT 4.3.0.Beta2 respin-a.
> [FeedHenry] Unable to copy fhconfig.json template to project
> ------------------------------------------------------------
>
> Key: JBIDE-20318
> URL: https://issues.jboss.org/browse/JBIDE-20318
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.0.Beta2
> Reporter: Pavol Srna
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.3.0.Beta2
>
>
> {code}
> java.io.IOException: Cannot find /res/templates/fhconfig.json
> at org.eclipse.core.internal.runtime.FindSupport.openStream(FindSupport.java:275)
> at org.eclipse.core.runtime.FileLocator.openStream(FileLocator.java:189)
> at org.jboss.tools.feedhenry.ui.internal.IntegrateFeedhenrySDKOperation.integrateFHConfigFile(IntegrateFeedhenrySDKOperation.java:70)
> at org.jboss.tools.feedhenry.ui.internal.IntegrateFeedhenrySDKOperation.execute(IntegrateFeedhenrySDKOperation.java:57)
> at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:108)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:130)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.feedhenry.ui.cordova.internal.wizards.NewApplicationWizard.performFinish(NewApplicationWizard.java:134)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months