[JBoss JIRA] (JBIDE-21451) Application wizard: No projects nor server templates when launched from explorer context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21451?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21451:
------------------------------------------
cherry picked to master
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21451
> URL: https://issues.jboss.org/browse/JBIDE-21451
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 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:1329)
> 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)
> Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 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.GeneratedMethodAccessor81.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)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21451) Application wizard: No projects nor server templates when launched from explorer context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21451?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21451:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21451
> URL: https://issues.jboss.org/browse/JBIDE-21451
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 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:1329)
> 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)
> Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 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.GeneratedMethodAccessor81.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)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21433) Application wizard: No projects nor server templates when launched from explorer context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21433:
----------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21433
> URL: https://issues.jboss.org/browse/JBIDE-21433
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 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:1329)
> 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)
> Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 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.GeneratedMethodAccessor81.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)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21433) Application wizard: No projects nor server templates when launched from explorer context menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21433?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21433:
------------------------------------------
merged into jbosstools-4.3.x
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21433
> URL: https://issues.jboss.org/browse/JBIDE-21433
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 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:1329)
> 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)
> Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 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.GeneratedMethodAccessor81.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)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21451) Application wizard: No projects nor server templates when launched from explorer context menu
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21451:
----------------------------------------
Summary: Application wizard: No projects nor server templates when launched from explorer context menu
Key: JBIDE-21451
URL: https://issues.jboss.org/browse/JBIDE-21451
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Fix For: 4.3.1.Beta2
Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
!empty_project.png!
This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
Stack trace:
{code}
org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
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:1329)
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)
Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
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.GeneratedMethodAccessor81.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)
... 38 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3576) Add products that JBDSIS is supported against to the CSP
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-3576?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-3576:
--------------------------------------
[~leacu][~mhusnain] We don't need to add any BETA/Alpha information. We only support GA bits and these are the only things that need to go on a "Supported configurations page" otherwise people will start thinking we support BETA/Alpha bits because it's on a "Supported configurations page"
> Add products that JBDSIS is supported against to the CSP
> --------------------------------------------------------
>
> Key: JBDS-3576
> URL: https://issues.jboss.org/browse/JBDS-3576
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: documentation
> Affects Versions: 9.0.0.GA
> Reporter: Mustafa Musaji
> Assignee: Misha Ali
> Labels: Support
> Fix For: 9.1.0.Beta2
>
> Attachments: Tooling_Support.png
>
>
> On JBDSIS Supported configurations page [1], there is no mention of the products and the versions compatible. We should add which JBDSIS products are supported against which version of the tooling. i.e. JBDSIS 7.0.x only works with Fuse 6.1 and earlier.
> We need a full list from JBDSIS team of tested and supported products.
> [1] https://access.redhat.com/articles/1351903
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3576) Add products that JBDSIS is supported against to the CSP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-3576?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBDS-3576:
----------------------------------
Hey [~mhusnain] - this looks awesome! Do we want to add JBDSIS 9.0.0.Alpha2 for Mars or should we wait for 9.0.0.Beta1?
[~lhein] - could you verify the Fuse runtimes with the Fuse tooling in the IS versions mentioned?
> Add products that JBDSIS is supported against to the CSP
> --------------------------------------------------------
>
> Key: JBDS-3576
> URL: https://issues.jboss.org/browse/JBDS-3576
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: documentation
> Affects Versions: 9.0.0.GA
> Reporter: Mustafa Musaji
> Assignee: Misha Ali
> Labels: Support
> Fix For: 9.1.0.Beta2
>
> Attachments: Tooling_Support.png
>
>
> On JBDSIS Supported configurations page [1], there is no mention of the products and the versions compatible. We should add which JBDSIS products are supported against which version of the tooling. i.e. JBDSIS 7.0.x only works with Fuse 6.1 and earlier.
> We need a full list from JBDSIS team of tested and supported products.
> [1] https://access.redhat.com/articles/1351903
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3557) JBDS Installer should be EPL licensed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3557:
----------------------------------
If ASLv2 is acceptable as a compatible license to EPL, then I would think we don't have to relicense the izpack stuff.
If ASLv2 and LGPL in the installer's *output* is acceptable (but GPL is *unacceptable*) then we have to change the licenses in central/plugins/org.jboss.tools.central.themes -- multi-licensed somehow under EPL, *GPL*, LGPL, Apache v2 and BSD! -- but probably the rest of JBT is OK. I'll look for more examples of *GPL* code.
My only question here remains: if it's OK to ship a bundle (installer jar) which is created/distributed under EPL, how is it OK to include software inside that bundle which is under a DIFFERENT license? Seems a bit bait-and-switch to me... you accept EPL for the installer, but then suddenly you've got differently-licensed code on disk. [~fontana] ?
> JBDS Installer should be EPL licensed
> -------------------------------------
>
> Key: JBDS-3557
> URL: https://issues.jboss.org/browse/JBDS-3557
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer, legal
> Reporter: Ken Finnigan
> Assignee: Nick Boldt
> Fix For: 9.1.0.Beta2, 10.0.0.Alpha1
>
>
> For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months