[jbosstools-issues] [JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
[
https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-22803:
------------------------------------------
[~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to
determine whether a feature is (not) present. But if a try/fallback is hacky I believe we
should. We could possibly do it in the client library (and not in JBT) preventing
consumers from relying on versions.
I still believe that offering access to the version still could be a nice feature, already
if its just for display purposes.
Explorer: When OS projects are created and deleted, seems Openshift
explorer restores non existing values
---------------------------------------------------------------------------------------------------------
Key: JBIDE-22803
URL: https://issues.jboss.org/browse/JBIDE-22803
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM2
Reporter: Jeff MAURY
Assignee: Dmitrii Bocharov
Labels: explorer, openshift, openshift_v3
Fix For: 4.4.2.AM2
Attachments: after application creation.png, after build finished.png, Openshift
Web Console.png, screenshot-1.png
EXEC: create an Openshift project
EXEC: expand it
EXEC: Create an application in this project (nodejs-example)
ASSERT: wait for the pod to be available
EXEC: delete the Openshit project
EXEC: create an Openshift project (using the same name. You may have to repeat this step
as you may got error that it still exists)
EXEC: expand it
EXEC: Create an application in this project (nodejs-example)
EXEC: expand the nodejs-example node
ASSERT: you should see 2 pods the old one and the build pod you just created:
[^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)