[
https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-23150 at 10/6/16 4:24 PM:
-------------------------------------------------------------------
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a
conceptual "limitation" to what we would erroneously expect of it. Rejecting as
*NOT_A_BUG*.
was (Author: adietish):
[~bdshadow] good finding. Yes, I believe that you're right. This is not a bug but a
conceptual "limitation" to what we would expect of it. Rejecting as
*NOT_A_BUG*.
Properties: wont show OpenShift properties if stacked in same
container as OpenShift explorer
---------------------------------------------------------------------------------------------
Key: JBIDE-23150
URL:
https://issues.jboss.org/browse/JBIDE-23150
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.Final
Reporter: Andre Dietisheim
Assignee: Dmitrii Bocharov
Labels: properties
Fix For: 4.4.2.AM2
Attachments: openshift-explorer-and-properties-both-stacked.png,
properties-empty.png
If you have the OpenShift explorer and the Properties view both stacked in the same view
like it is shown in the following screenshot:
!openshift-explorer-and-properties-both-stacked.png!
and you start up Eclipse with the Properties view visible (not OpenShift explorer) you
wont be able to ever see any property of any OpenShift resource. The properties view
always stays empty.
steps to reproduce:
# ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual
container
# ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
# EXEC: make Properties view visible
# EXEC: make OpenShift explorer visible. Select an entry
# EXEC: switch back to Properties view
Result:
Properties view stays empty. You can switch back and forth, you wont get any content in
the properties view.
!properties-empty.png!
Only moving Properties view to a different (visual) container helps.
the steps simply show a reliable way to reproduce it. I think there are more cases where
this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)