Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-22612

Explorer: OpenShift connections are missing from the explorer on startup

    XMLWordPrintable

Details

    • devex #116 June 2016
    • 2
    • Hide
      1. ASSERT: have at least 1x v3 and 1x v2 Connection
      2. ASSERT: have a clean workspace (no server adapters nor other references to the OpenShift plugins)
      3. EXEC: launch Eclipse
      4. ASSERT: look at OpenShift Explorer view and verify that your connections are listed, both of them

      Result:
      None is listed

      Show
      ASSERT: have at least 1x v3 and 1x v2 Connection ASSERT: have a clean workspace (no server adapters nor other references to the OpenShift plugins) EXEC: launch Eclipse ASSERT: look at OpenShift Explorer view and verify that your connections are listed, both of them Result: None is listed
    • Workaround Exists
    • Hide

      launch OpenShift Connection wizard. As soon as the wizard shows up the v3 connections are listed. V2 connections are still missing.

      Show
      launch OpenShift Connection wizard. As soon as the wizard shows up the v3 connections are listed. V2 connections are still missing.

    Description

      After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer.

      This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded.

      Before JBIDE-21828, getExplorerElements would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-22615 Explorer: Connections should get loaded from extension points

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              adietish@redhat.com André Dietisheim
              fbricon@redhat.com Fred Bricon
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: