[JBoss JIRA] (JBIDE-21805) Delete of OpenShift application via server adapter is disabled
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21805?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21805.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> Delete of OpenShift application via server adapter is disabled
> --------------------------------------------------------------
>
> Key: JBIDE-21805
> URL: https://issues.jboss.org/browse/JBIDE-21805
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.4.0.Alpha1
>
> Attachments: video.ogg-1.ogv
>
>
> Earlier it was possible to delete an OpenShift application via context menu of a server adapter "OpenShift" - "Delete application(s)...". While fixing JBIDE-21563, binding was commented out and some changes were done. Currently the context menu item is disabled so it is not possible to delete application via context menu item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21515) Explorer: New deployments and pods dont refresh properly in explorer tree
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21515?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21515.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> Explorer: New deployments and pods dont refresh properly in explorer tree
> -------------------------------------------------------------------------
>
> Key: JBIDE-21515
> URL: https://issues.jboss.org/browse/JBIDE-21515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: openshift_deployment_view
> Fix For: 4.4.0.Alpha1
>
> Attachments: Service_added_but_shows_empty_space.png
>
>
> Expanding the explorer tree of a project to see the deployments and pods and then adding a new deployment from the server causes the display to show the wrong nodes and not receive any updates. See screen shot attached:
> Demonstrated by:
> # From eclipse, add a new project
> # Expand project . note: no deployments
> # From cli, add a service
> # Note screen 'updates' but there is no deployment, just an empty node.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ]
Radim Hopp edited comment on JBIDE-21720 at 5/3/16 6:54 AM:
------------------------------------------------------------
Default route, selected on "Server Settings" page of new server adapter wizard, is not respected. I've made a little screencast demonstrating this: https://youtu.be/ctehkx9OPek
In this screencast I have two routes (eap-app and my-route). "my-route" is selected in new server adapter wizard, but when I click show in browser, eap-app route is opened (eap-app-sample-project.rhel-cdk.10.1.2.2.xip.io)
was (Author: rhopp):
Default route, selected on "Server Settings" page of new server adapter wizard is not respected. I've made a little screencast demonstrating this: https://youtu.be/ctehkx9OPek
In this screencast I have two routes (eap-app and my-route). "my-route" is selected in new server adapter wizard, but when I click show in browser, eap-app route is opened (eap-app-sample-project.rhel-cdk.10.1.2.2.xip.io)
> Server Adapter: user choose default route when creating the server
> ------------------------------------------------------------------
>
> Key: JBIDE-21720
> URL: https://issues.jboss.org/browse/JBIDE-21720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available.
> I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21798) ExplorerViewTabbedPropertyAdapterFactory is incorrectly referenced in org.jboss.tools.openshift.ui.plugin.xml
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21798?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21798.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> ExplorerViewTabbedPropertyAdapterFactory is incorrectly referenced in org.jboss.tools.openshift.ui.plugin.xml
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21798
> URL: https://issues.jboss.org/browse/JBIDE-21798
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, properties
> Fix For: 4.4.0.Alpha1
>
>
> 1. Run JBDS without org.jboss.tools.openshift.express.ui plugin.
> 2. Open OpenShift Explorer and Properties views.
> 3. Select a connection.
> Tabbed property sheet is not loaded in Properties, and Error log has entry:
> {code}
> !MESSAGE Plug-in org.jboss.tools.openshift.ui was unable to load class org.jboss.tools.openshift.internal.ui.property.tabbed.ExplorerViewTabbedPropertyAdapterFactory.
> !STACK 0
> java.lang.ClassNotFoundException: org.jboss.tools.openshift.internal.ui.property.tabbed.ExplorerViewTabbedPropertyAdapterFactory cannot be found by org.jboss.tools.openshift.ui_3.2.0.qualifier
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:554)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.core.internal.adapter.AdapterFactoryProxy.loadFactory(AdapterFactoryProxy.java:136)
> at org.eclipse.core.internal.adapter.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:81)
> at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:295)
> at org.eclipse.ui.part.WorkbenchPart.getAdapter(WorkbenchPart.java:143)
> at org.eclipse.ui.navigator.CommonNavigator.getAdapter(CommonNavigator.java:462)
> at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:59)
> at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:94)
> at org.eclipse.ui.views.properties.PropertySheet.doCreatePage(PropertySheet.java:199)
> at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:400)
> at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:743)
> at org.eclipse.ui.views.properties.PropertySheet.partActivated(PropertySheet.java:291)
> at org.eclipse.ui.part.PageBookView$4.partActivated(PageBookView.java:1043)
> at org.eclipse.ui.internal.WorkbenchPage$15.run(WorkbenchPage.java:4909)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4906)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4885)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:207)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:245)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:242)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:724)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.switchPerspective(PartServiceImpl.java:625)
> at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.showTab(PerspectiveStackRenderer.java:106)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:103)
> at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.postProcess(PerspectiveStackRenderer.java:63)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:670)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:729)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:723)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:707)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72)
> at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:151)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:729)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:723)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:707)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72)
> at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:614)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:729)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:723)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:707)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1066)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21599) Source path validation does not work properly in new server adapter wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21599?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21599.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> Source path validation does not work properly in new server adapter wizard
> --------------------------------------------------------------------------
>
> Key: JBIDE-21599
> URL: https://issues.jboss.org/browse/JBIDE-21599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> When using eclipse path properties in source path in New Server wizard for a new OpenShift 3 server adapter, validation does not work properly. E.g. I choose a workspace project by browsing workspace and choosing it, it fill into the text widget for source path
> {code}
> ${workspace_loc:/org.jboss.tools.openshift.ui.bot.test}
> {code}
> and it is OK, next button is enabled. But if I cut/paste it there again or if I type workspace location manually, not via browsing workspace project, it is validated as incorrect path and it is not possible to proceed through wizard.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21789.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v2
> Fix For: 4.4.0.Alpha1
>
> Attachments: openshift-3-connections-listed.png
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be.
> !openshift-3-connections-listed.png!
> If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21837.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> OpenShift server adpter editor: link 'Open launch configuration' throws exception
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21837
> URL: https://issues.jboss.org/browse/JBIDE-21837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2, openshift_v3, server_adapter_editor
> Fix For: 4.4.0.Alpha1
>
> Attachments: ErrorAtEditLaunchConfig.png
>
>
> There is no launch configuration tab groups bound to the openshift launch type.
> As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'.
> This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21566) [regression] Explorer: (Multiple application) deletion does not work anymore
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21566?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21566.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> [regression] Explorer: (Multiple application) deletion does not work anymore
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21566
> URL: https://issues.jboss.org/browse/JBIDE-21566
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v2, respin-a
> Fix For: 4.4.0.Alpha1
>
>
> Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one.
> Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21595) Port Forwarding: Caching of checkbox for free port does not work properly
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21595?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21595.
---------------------------------
Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264.
> Port Forwarding: Caching of checkbox for free port does not work properly
> -------------------------------------------------------------------------
>
> Key: JBIDE-21595
> URL: https://issues.jboss.org/browse/JBIDE-21595
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.4.0.Alpha1
>
>
> In JBIDE-21123 was fixed caching of the checkbox for usage of free ports in case of inactivity of port forwarding. But upon checking the checkbox to use free ports and start port forwarding, closing wizard and reopening port forwarding wizard, port forwarding is still active using free ports but the checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months