[
https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi...
]
Dmitrii Bocharov edited comment on JBIDE-22803 at 10/6/16 6:29 PM:
-------------------------------------------------------------------
[~jcantrill] [~adietish]
* possibly it is a bug, but anonymous user can't see the version
* definitely changes in restclient are needed. And while playing with Watch manager i
found all these things.
* yes, i agree that this logic is in jbt. And there is a restart method in
WatchManager.WatchListener. And i was asking about the comment: _// TODO enhance fix to
only check project once_ in the restart() method of Watch. What are the cases where
watching needs to get restarted?
* ok, it's just a pitty that my searches about version logic were useless. Alexey and
Andre both told me that it would be a useful feature. Strangely we didn't know about
this design decision. About "'try' to watch projects and fall back" -
this is one of the ways i wrote about above, and that i thought was a hack. Please have a
look.
was (Author: dbocharov):
* possibly it is a bug, but anonymous user can't see the version
* definitely changes in restclient are needed. And while playing with Watch manager i
found all these things.
* yes, i agree that this logic is in jbt. And there is a restart method in
WatchManager.WatchListener. And i was asking about the comment: _// TODO enhance fix to
only check project once_ in the restart() method of Watch. What are the cases where
watching needs to get restarted?
* ok, it's just a pitty that my searches about version logic were useless. Alexey and
Andre both told me that it would be a useful feature. Strangely we didn't know about
this design decision. About "'try' to watch projects and fall back" -
this is one of the ways i wrote about above, and that i thought was a hack. Please have a
look.
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)