[
https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-15205:
------------------------------------------
I watched OpenShift UI plugin getting started and found out that it gets awaken via the
OpenShift Server adapter. Chatting to Rob and Rob chatting to Paul Webster we found out
that bundle started-states may be persisted if specific osgi API's are used.
Apparently these are used in ASTools:
{quote}
5:07:23 PM] … <paulweb515> rawbdor: yes (but no :-)
<paulweb515> rawbdor: if a bundle is started due to classloading (something caused a
class to load) then it won't automatically start during the next sessions until
another class gets loaded
<paulweb515> rawbdor: if someone starts a bundle using org.osgi.framework.Bundle and
doesn't use org.osgi.framework.Bundle.START_TRANSIENT that bundle *will* be started on
the next session startup
{quote}
OpenShift menu contribution issue
---------------------------------
Key: JBIDE-15205
URL:
https://issues.jboss.org/browse/JBIDE-15205
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.1.0.CR1
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 4.1.1.Final, 4.2.0.Alpha1
Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png,
project-explorer-nonopenshift.png, project-explorer-openshift.png
The OpenShift menu contribution is visible when right-clicking any Eclipse project (not
only an OpenShift project).
The issue happens because the
org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester
isn't declared correctly.
Also, its icon (marker.png) is too large for a context menu action.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira