]
Jeff MAURY commented on JBIDE-22810:
------------------------------------
Managed to reproduce it with the dev env.
This is design problem. The connections are stored in *ConnectionsRegistry* (from bundle
_org.jboss.tools.openshift.common.core_) but this registry is filled by the bundles
activators (_org.jboss.tools.openshift.core_ and
_org.jboss.tools.openshift.express.core_).
So if no classes are loaded from those bundles, then the registry is not filled.
Solution is to switch to components or extension points
OpenShift Explorer: empty at start
----------------------------------
Key: JBIDE-22810
URL:
https://issues.jboss.org/browse/JBIDE-22810
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM1
Environment: windows
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Labels: explorer, openshift_v3, windows
Fix For: 4.4.2.Final
Attachments: EmptyViewAtStart.png
When I close Eclipse with OpenShift Explorer not visible (by selecting another view in
the same area of the workbench, or by switching another perspective), after I reopen
Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for
authenticating any available connection, it happens successfully, but the view remains
empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
I have to add that it is not 100% reproducible. What is interesting, when starting it in
the debugger, I reproduce it around 80%, while in normal run the probability is very low
if do it leisurely, but can be increased to 50% if take the task with some dedication and
find the right moment (very soon after the window opens) to select the explorer.