Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Subversive Capabilities Location

In Galileo, the Subversive Capabilities plug-in was included as part of the package process. In Helios, capabilities were pulled out of that process and to be documented separately. The goal of this document is to explain where to find the existing Capabilities plug-in in SVN.

The existing Capabilities plug-in can be found in SVN: http://dev.eclipse.org/svnroot/technology/org.eclipse.subversive/trunk/org.eclipse.team.svn.ui.capabilities. Really all that's in this plug-in is the org.eclipse.ui.activities extension point in the plugin.xml at this point. All that the extension does is shut down the Subversive plug-ins:

  
   <extension point="org.eclipse.ui.activities">   
      <activity
      	    name="%activity.team.svn"
      	    id="org.eclipse.team.svn"      		
            description="%activity.team.svn.desc">                                    
      </activity>     
 
      <activityPatternBinding
            activityId="org.eclipse.team.svn"
            pattern="org\.eclipse\.team\.svn\.ui/.*">
      </activityPatternBinding>

      <activityPatternBinding
            activityId="org.eclipse.team.svn"
            pattern="org\.eclipse\.team\.svn\.core/.*svnnature">
      </activityPatternBinding>

      <activityRequirementBinding
            activityId="org.eclipse.team.svn"
            requiredActivityId="org.eclipse.team">
      </activityRequirementBinding>

      <!-- Subversive in Team category -->
      <categoryActivityBinding
            activityId="org.eclipse.team.svn"
	    categoryId="org.eclipse.categories.teamCategory">
      </categoryActivityBinding>    
	
      <!-- Subversive capability enabled by default -->
      <defaultEnablement
            id="org.eclipse.team.svn">
      </defaultEnablement>             
   </extension>   
   

To actually make use of these sample capability definitions, an adopter or product needs to "bind" them, "enable" them, and fit them into some preference page for capabilities.

Back to the top