]
Andre Dietisheim commented on JBIDE-22612:
------------------------------------------
IMHO the view should always be the trigger for any loading (and thus plugin activation) to
happen. If there's no view, no plugin (neither ui nor core) should get activated nor
loaded. Since the org.jboss.tools.openshift.core plugin is set to get activated when one
of it's classes is accessed (Bundle-ActivationPolicy: lazy) I suspect the v3 content
provider no to access any of the v3 core classes.
Explorer: OpenShift v3 connections are missing from the explorer on
startup
---------------------------------------------------------------------------
Key: JBIDE-22612
URL:
https://issues.jboss.org/browse/JBIDE-22612
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.1.Alpha1
Reporter: Fred Bricon
Labels: explorer, openshift_v3
Fix For: 4.4.1.Alpha1
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|https://github.com/jbosstools/jbosstools-openshift/co...]
would return all the OpenShift3 connections. With the new code, the UI Model is expected
to be already loaded