[
https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich updated JBIDE-21563:
------------------------------------------
Description:
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.
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.
was: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.
[regression] Explorer: (Multiple application) deletion does not work
anymore
----------------------------------------------------------------------------
Key: JBIDE-21563
URL:
https://issues.jboss.org/browse/JBIDE-21563
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
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.
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)