[
https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-15205:
---------------------------------------
I think this is a bug in the Eclipse command framework.
If a declaration contains forcePluginActivation="true", a plugin would need to
be activated when calling its property tester.
That seems to work correctly if a property tester is called within a menu contribution,
but if it is called within a command contribution, it doesn't work always.
OpenShift menu contribution issue
---------------------------------
Key: JBIDE-15205
URL:
https://issues.jboss.org/browse/JBIDE-15205
Project: Tools (JBoss Tools)
Issue Type: Bug
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