OTCapabilities

Adding capability configurability to the OTDT

If the Object Teams Development Environment shall be included in a product a definition of "capabilities" can be used to optionally hide most of its UI contributions.

For this task a snippet like this should be added to a plugin.xml:

     <extension
         point="org.eclipse.ui.activities">
      <activity
            description="Develop OT/J applications (Object Teams)"
            id="org.eclipse.objectteams.otjDevelopment"
            name="OT/J Development">
      </activity>
      <activityRequirementBinding
            activityId="org.eclipse.objectteams.otjDevelopment"
            requiredActivityId="org.eclipse.javaDevelopment">
      </activityRequirementBinding>
      <activityPatternBinding
            activityId="org.eclipse.objectteams.otjDevelopment"
            isEqualityPattern="false"
            pattern="org\.eclipse\.objectteams\.otdt\.ui/.*">
      </activityPatternBinding>
      <activityPatternBinding
            activityId="org.eclipse.objectteams.otjDevelopment"
            isEqualityPattern="false"
            pattern="org\.eclipse\.objectteams\.otdt\.ui\..*/.*">
      </activityPatternBinding>
      <categoryActivityBinding
            activityId="org.eclipse.objectteams.otjDevelopment"
            categoryId="org.eclipse.categories.developmentCategory">
      </categoryActivityBinding>
      <defaultEnablement
            id="org.eclipse.objectteams.otjDevelopment">
      </defaultEnablement>
   </extension>

This assumes that an "activity" org.eclipse.javaDevelopment has been defined in the way it exists in the Eclipse SDK.

If no default enablement shall be used, care must be taken that the wizards in category org.eclipse.objectteams.otdt.ui.wizards are excluded from the above activityPatternBinding. Also those wizards should probably be defined as triggers for enabling the capability as a means for progressive discovery.