[jbosstools-issues] [JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

Jeff MAURY (JIRA) issues at jboss.org
Mon Nov 21 11:10:00 EST 2016


    [ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13325800#comment-13325800 ] 

Jeff MAURY commented on JBIDE-22810:
------------------------------------

That is not related to platforms. On my Win10 machine, I had immediatly the problem with DevStudio 10.2.0.AM3 and had to close some windows/perspectives on my dev env. So I think it is more related to the environment than the platform

> 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. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list