This is the menu that appears when you right click any of the enabled resources in the viewer:

The different areas correspond to different insertion points in the viewer definition and the contributions to those insertion points (except for the ‘additions’ insertion point that corresponds to the area marked in blue in the picture) are either done by existing activity providers following the patterns org.eclipse.ui.navigator.resources.* (and contributed by the org.eclipse.ui.navigator.resource plugin) or new activity providers, following the pattern com.ibm.btt.tools.projectexplorer.*, that either add new actions to the menu, as the Generate Runtime View action

or override the behavior of other action providers, as for the Properties action

For the ‘additions’ insertion point, the decision has been to allow all platform contributions and then filter them using the org.eclipse.ui.activities extension point. As an example, the Team action set should not appear for specific type of resources; this is defined as follows:

A property tester verifies if the type of resource is valid and returns a boolean value that will be used to either show or not the entry in the context menu. The property tester is defined with the org.eclipse.core.expressions.propertyTesters:

The activityPatternBinding property identifies the id of the actions that will be removed if the selected resource matches the conditions ( in the example, we are eliminating in certain cases all actions which id starts by org.eclipse.team.ui):

In order to remove any other plugin contribution to the ‘additions’ insertion point, refer to the Eclipse documentation about Activities (org.eclipse.ui.activities), activities binding patterns (the pattern matching used in activity pattern bindings follows the rules described in the java.util.regex package for regular expressions) and filtering conditions.