[
https://issues.jboss.org/browse/JBIDE-10818?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10818:
-------------------------------------
Fix Version/s: 3.3.0.CR1
(was: 3.3.0.Beta3)
moved this to CR1 since the user-visible pain-points are not harming much yet.
OpenShift Express Console: different jobs have to block each other
-------------------------------------------------------------------
Key: JBIDE-10818
URL:
https://issues.jboss.org/browse/JBIDE-10818
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Xavier Coulon
Fix For: 3.3.0.CR1
The *OpenShift Express Console* allows you to delete applications, create new
applications and will allow you to refresh the view. Those operations are executed in
background jobs so that the Eclipse UI is not blocked in the meantime. We therefore have
to setup scheduling rules on those jobs so that a refresh will wait until the delete is
finished. To me the best way to achieve this is to create cathegories of jobs (ex.
ApplicationJob, UserJob, etc.) that have the appropriate scheduling rules initialized (ex.
ApplicationJobs operate on applications and therefore have to block UserJob that possibly
operate on all applications.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira