bundles/org.eclipse.pde.doc.user/contexts_PDE.xml

<?xml version="1.0" encoding="UTF-8"?>
<?NLS TYPE="org.eclipse.help.contexts"?>
<contexts>

<!-- Actions -->
	<context id="update_classpath">
		<description>PDE computes the classpath of this project by looking for dependencies in the workspace and enabled external plug-ins and fragments.</description>
		<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
   		<topic label="Configuring PDE" href="guide/pde_configuring.htm"/>
		<topic label="Self-hosting" href="guide/pde_selfhosting.htm"/>
	</context>
	<context id="open_dependencies">
		<description>This command opens the Dependencies view to show all the plug-ins needed to run the selected plug-in.</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
   		<topic label="Configuring PDE" href="guide/pde_configuring.htm"/>
		<topic label="Self-hosting" href="guide/pde_selfhosting.htm"/>
	</context>	
	<context id="find_references">
		<description>This command searches for all the plug-ins that directly depend on the selected plug-in and all the fragments which target it.</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
		<topic label="Fragments" href="guide/pde_fragment.htm"/>
	</context>
	<context id="create_plugin_jars">
		<description>This command builds an Ant script which can then be used to build an executable version of the plug-in.</description>
		<topic label="Generating Ant Scripts" href="guide/pde_feature_generating_ant.htm"/>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
	</context>
	<context id="create_fragment_jars">
		<description>This command builds an Ant script which can then be used to build an executable version of the fragment.</description>
		<topic label="Generating Ant Scripts" href="guide/pde_feature_generating_ant.htm"/>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
	</context>
	<context id="create_feature_jars">
		<description>This command builds an Ant script which can then be used to build a feature.</description>
		<topic label="Features" href="guide/pde_features.htm"/>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
		<topic label="Creating the JARs" href="guide/pde_feature_generating_jars.htm"/>
	</context>	
		
<!-- Dialogs -->
 	<context id="fragment_add_target">
 		<description>This wizard allows you to select the target plug-in for your fragment.</description>
		<topic label="Fragments" href="guide/pde_fragment.htm"/>
	</context>
	<context id="build_add_variable">
		<description>This wizard allows you to add variables that drive the build process.</description>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
	</context>	
	<context id="schema_type_restriction">
		<description>This wizard allows to define the possible values for the selected attribute.</description>
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
	</context>
	<context id="search_page">
		<description>On this page, you can search for references to and declarations of plug-ins, fragments and extension points.
 The search can be extended beyond workspace resources to include external plug-ins. </description>
	</context>
	<context id="launcher_basic">
		<description>This page allows you to set the basic program arguments to run the configuration.</description>
		<topic label="Running a plug-in" href="guide/pde_running.htm"/>
	</context>
	<context id="launcher_advanced">
		<description>This page allows you to run your configuration with only a subset of the plug-ins.</description>
		<topic label="Choosing plug-ins to run" href="guide/pde_running_plugins.htm"/>
	</context>
	<context id="launcher_tracing">
		<description>This page allows you to use tracing flags that will cause tracing information to be printed to the standard output (or the console view) when you run the configuration.</description>
		<topic label="Running with tracing" href="guide/pde_running_tracing.htm"/>
	</context>

	<context id="source_attachment">
		<description>This dialogs allows you to associate the selected dynamic entry with the source archive in cases where PDE failed to make this association automatically.</description>
	</context>
	
<!-- Editors -->

	<context id="manifest_source_page">
		<description>This page allows you to edit the file content directly.</description>
		<topic label="Source page" href="guide/pde_manifest_source.htm"/>
	</context>
	<context id="manifest_welcome">
		<description>This page summarizes the content that was generated by the template.</description>
		<topic label="Welcome page" href="guide/pde_manifest_welcome.htm" />
	</context>		
	<context id="manifest_plugin_overview">
		<description>The Overview page shows you the plug-in at a glance.</description>
		<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm"/>
		<topic label="Overview page" href="guide/pde_manifest_overview.htm" />
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="manifest_plugin_dependencies">
		<description>The Dependencies page shows the dependencies that your plug-in has on other plug-ins.</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
		<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="manifest_plugin_runtime">
		<description>The Runtime page shows information about the plug-in's runtime libraries.</description>
		<topic label="Runtime page" href="guide/pde_manifest_runtime.htm" />
		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
	</context>
	<context id="manifest_plugin_extensions">
		<description>The Extensions page shows all the extensions used by your plug-in.</description>
		<topic label="Extensions page" href="guide/pde_manifest_extensions.htm" />
	</context>
	<context id="manifest_plugin_ext_points">
		<description>The Extension points page shows all the extension points declared by the plug-in.</description>
		<topic label="Extension points page" href="guide/pde_manifest_extensionpoints.htm" />
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
	</context>
	<context id="manifest_fragment_overview">
		<description>The Overview page shows you the fragment at a glance.</description>
		<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm"/>
		<topic label="Overview page" href="guide/pde_manifest_overview.htm" />
		<topic label="Fragments" href="guide/pde_fragment.htm"/>
		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
	</context>
	<context id="manifest_fragment_dependencies">
		<description>The Dependencies page shows the dependencies that your fragment has on other plug-ins.</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
		<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
		<topic label="Fragment example" href="guide/pde_fragment_example.htm"/>
	</context>
	<context id="manifest_fragment_runtime">
		<description>The Runtime page shows information about the fragment's runtime libraries.</description>
		<topic label="Runtime page" href="guide/pde_manifest_runtime.htm" />
		<topic label="Generating Ant Build Scripts" href="guide/pde_feature_generating_ant.htm"/>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
	</context>
	<context id="manifest_fragment_extensions">
		<description>The Extensions page shows all the extensions used by your fragment.</description>
		<topic label="Extensions page" href="guide/pde_manifest_extensions.htm" />
	</context>
	<context id="manifest_fragment_ext_points">
		<description>The Extension points page shows all the extension points declared by the fragment.</description>
		<topic label="Extension points page" href="guide/pde_manifest_extensionpoints.htm" />
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
	</context>
	<context id="build_page">
		<description>This editor is used to edit the build configuration for a plug-in, fragment or a feature.</description>
		<topic label="Build configuration" href="guide/pde_feature_generating_build.htm"/>
	</context>
	<context id="schema_editor_main">
		<description>This editor creates a schema for an extension point, to which all extensions extending this point must conform.</description>
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
	</context>
	<context id="schema_editor_doc">
		<description>Documentation for the use of this extension point is entered on this page.</description>
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
	</context>
	<context id="manifest_feature_overview">
		<description>This page shows general information about the feature.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
		<topic label="Features" href="guide/pde_features.htm"/>
		<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>
		<topic label="Deploying a Feature" href="guide/pde_feature_generating.htm"/>
		<topic label="Creating the JARs" href="guide/pde_feature_generating_jars.htm"/>
	</context>
	<context id="manifest_feature_info">
		<description>This page is used to edit the required description, license and copyright information.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	</context>
	<context id="manifest_feature_content">
		<description>This page shows the list of plug-ins and fragments that are included in the feature.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
		<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>
	</context>
	<context id="manifest_feature_advanced">
		<description>This page lists all features included in this feature</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	</context>	
	<context id="feature_synchronize_versions">
		<description>The versions of the plug-ins and fragments should be synchronized with that of the packaged feature.</description>
		<topic label="Synchronizing versions" href="guide/pde_feature_synchronizing.htm"/>
	</context>
	
	// Site Editor
	<context id="manifest_site_overview" >
		<description>This page shows the general information about the update site.</description>
		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
		<topic label="Update site editor" href="guide/pde_site_editor.htm"/>
		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
	</context>
	<context id="manifest_site_build">
		<description>This page allows you to configure how this site will be built from features and plug-ins in the workspace.</description>
		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
		<topic label="Update site editor" href="guide/pde_site_editor.htm"/>
		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
	</context>
	<context id="manifest_site_features">
		<description>This page lists all the features visible to the user when connecting to this site.</description>
		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
		<topic label="Update site editor" href="guide/pde_site_editor.htm"/>
		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
	</context>
	<context id="manifest_site_archives">
		<description>This page lists all the archive mappings in this site.</description>
		<topic label="Setting up an update site project" href="guide/pde_site_setup.htm"/>
		<topic label="Update site editor" href="guide/pde_site_editor.htm"/>
		<topic label="Building plug-ins and features using update site editor" href="guide/pde_site_building.htm"/>
	</context>
	<context id="new_category_def_dialog">
		<description>This dialog defines a new or edits an existing feature category definition.</description>
	</context>
		

<!-- Preference pages -->
   <context  id="main_preference_page" >
      <description>This page allows you to set Plug-in Development Environment general settings.</description>
   	<topic label="Configuring PDE" href="guide/pde_configuring.htm"/>
   </context>
   
   <context  id="buildpath_preference_page" >
      <description>This page allows you to control when the Java classpath computation is performed automatically. 
 Automatic computation of the classpath for the listed changes will keep your classpath in sync with the rest of the files, ensuring that your plug-in only sees classes that it will see at run-time.
 You can also optionally use Java classpath containers to manage classpath entries added for dependent plug-ins. This ensures greater flexibility when self-hosting.</description>
 	<topic label="Self-hosting" href="guide/pde_selfhosting.htm"/>
	<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
   </context>
   
   <context id="compilers_preference_page" >
      <description>This page allows you to specify the behaviour of
      the various manifest compilers.
      </description>
	  <topic label="Source page" href="guide/pde_manifest_source.htm"/>
   </context>
   
   <context  id="editor_preference_page" >
      <description>This page allows you to configure behaviour and presentation of PDE multi-page editors.</description>
	<topic label="Plug-in manifest editor" href="guide/pde_manifest.htm"/>
	<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
   </context>
   
   <context  id="source_preference_page" >
      <description>This page allows you to configure source code locations.
 When attaching source archives to Java libraries, PDE first looks in plug-ins. If not found, the search is extended to source locations. 
 Source locations can be provided by plug-ins that are used to carry source code (in SDKs). They can also be defined by users. 
 Disabled source locations will be ignored by PDE.</description>
	<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm"/>
	<topic label="Binary project self-hosting" href="guide/pde_selfhosting_binary.htm"/>
   </context>
   
    <context  id="target_environment_preference_page" >
      <description>This page allows you set the target enviroment for the plug-ins you develop.
 Target environment settings affect class path computation and are passed to the run-time workbench instance by the launcher.</description>
	<topic label="Self-hosting" href="guide/pde_selfhosting.htm"/>
	<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
 	<topic label="Running a plug-in" href="guide/pde_running.htm"/>
	<topic label="Binary project self-hosting" href="guide/pde_selfhosting_binary.htm"/>
   </context>
   
   <context  id="target_platform_preference_page" >
      <description>This page allows you to configure the target platform that will be used to develop against. 
 PDE will look for plug-ins and fragments in the target platform and will mix them with plug-ins in the workspace. 
 In a case when the same plug-in exists in the workspace and in the target platform, the duplication can be resolved by disabling external copy (in the target platform).</description>
   	<topic label="Configuring PDE" href="guide/pde_configuring.htm"/>
	<topic label="Self-hosting" href="guide/pde_selfhosting.htm"/>
	<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm"/>
	<topic label="Binary project self-hosting" href="guide/pde_selfhosting_binary.htm"/>
   </context>

<!-- Property pages -->	

<!-- Views -->	
	<context  id="plugins_view">
		<description>The Plug-in View show the plug-ins and fragments that will be passed to the runtime workbench when running or debugging.
If simple self-hosting is used, the view allows you to browse external plug-ins that are not part of the workspace.</description>
		<topic label="Concepts" href="guide/pde_concepts.htm"/>
   		<topic label="Configuring PDE" href="guide/pde_configuring.htm"/>
		<topic label="Self-hosting" href="guide/pde_selfhosting.htm"/>
	 </context>
	 <context id="dependencies_view">
	 	<description>The Dependencies view shows all the plug-ins required to run the selected plug-in</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
		<topic label="Running a plug-in" href="guide/pde_running.htm"/>
	</context>
	<context id="registry_view">
		<description>The Plug-in Registry view shows a read-only view of the plug-in registry of the running platform</description>
		<topic label="Setting up the workbench" href="guide/pde_setup.htm"/>
	</context>
	<context id="log_view">
		<description>The log view captures warnings and internal errors thrown by the internal platform or your code</description>
		<topic label="Setting up the workbench" href="guide/pde_setup.htm"/>
	</context>
		
		
<!-- Wizard pages -->
	<context id="new_project_structure_page">
		<description>This wizard helps you create a new plug-in project.
 If the plug-in is to contain resources only, create a simple project.
 Otherwise, create a Java project.</description>
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="new_fragment_structure_page">
		<description>This wizard helps you create a new fragment project.
 If the fragment is to contain resources only, create a simple project.
 Otherwise, create a Java project.</description>
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="new_project_code_gen_page">
		<description>The blank plug-in option results in the creation of a plug-in project containing a manifest file with minimal content.
 For a quick start, use the code generation wizards to create a plug-in project containing a working extension.
 You can customize a plug-in to contain any combination of the available extension templates by choosing the 'Custom Plug-in Wizard' option.</description>
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="new_fragment_code_gen_page">
		<description>Fragments are additions to plug-ins.  If you know the plug-in you are targeting, choose the 'Default Fragment Structure' wizard and proceed.
 The blank fragment option results in the creation of a fragment without a target plug-in.  This fragment is non-functional until you later edit the manifest file and add the target plug-in data.</description>
		<topic label="Fragments" href="guide/pde_fragment.htm"/>
	</context>
	<context id="new_project_required_data">
		<description>Data entered on this page is used to customize the generated manifest file and top level plug-in Java class.</description>
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="new_fragment_required_data">
		<description>This page specifies the fragment's target plug-in and other data required to generate the manifest file.</description>
		<topic label="Fragments" href="guide/pde_fragment.htm"/>
	</context>	
	<context id="new_feature_data">
		<description>This page specifies basic data about the feature.</description>	
		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
		<topic label="Features" href="guide/pde_features.htm"/>
		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
	</context>
	<context id="new_feature_referenced_plugins">
		<description>The plug-ins and fragments selected on this page will packaged in the feature.</description>
		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
		<topic label="Features" href="guide/pde_features.htm"/>
		<topic label="Setting up a feature project" href="guide/pde_feature_setup.htm"/>
	</context>
	<context id="new_schema">
		<description>All extensions that extend the specified extension point will be validated against this schema.</description>
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
		<topic label="Extension point schema editor" href="guide/pde_schema_editor.htm"/>
		<topic label="Using extension point schema" href="guide/pde_schema_using.htm"/>
	</context>
	<context id="converted_projects">
		<description>Select Java projects to which you want to add PDE capabilities.
 If the selected project does not contain a manifest file, PDE will generate a generic one.
 It is recommended that you uncheck the update build path option if your project does not contain a build.properties file.</description>
		<topic label="Converting existing projects" href="guide/pde_convert.htm"/>
	</context>	
	<context id="plugin_import_first_page">
		<description>The default location to import from is the target platform specified on the Target Platform preference page.
 If you choose to import with source from a different location, you have to manually add the source locations for the plugins you choose to the Source Code Locations page.</description>	
	 	<topic label="Binary project self-hosting" href="guide/pde_selfhosting_binary.htm"/>
	</context>
	<context id="plugin_import_second_page">
		<description>This list shows the plug-ins and fragments found in the location specified on the previous page.</description>
	 	<topic label="Binary project self-hosting" href="guide/pde_selfhosting_binary.htm"/>
	</context>
	<context id="feature_import_first_page">
		<description>This page defines the location from which the features will be imported into the workspace. This wizard
should only be used in conjunction with feature-based self-hosting.</description>	
	</context>
	<context id="feature_import_second_page">
		<description>This list shows the features found in the location specified on the previous page.</description>
	</context>
	<context id="template_selection">
		<description>Customize the plug-in by choosing one or more template extensions.</description>
	</context>		
	<context id="template_editor">
		<description>This template creates a sample XML editor with basic editing capabilities, syntax highlighting, etc.</description>
	</context>
	<context id="template_hello_world">
		<description>This template creates a sample action set that adds a menu to the menu bar and a button to the toolbar.</description>
	</context>
	<context id="template_help">
		<description>This template creates a sample Help Table of Contents.</description>
	</context>
	<context id="template_multipage_editor">
		<description>This template creates a multi-page editor that works on files with the chosen extension.</description>
	</context>
	<context id="template_new_wizard">
		<description>This template creates a wizard that can create a new file in the workspace</description>
	</context>
	<context id="template_perspective_extensions">
		<description>This template adds an action set and other shortcuts to the chosen target perspective.</description>
	</context>
	<context id="template_popup_menu">
		<description>This template adds a popup menu to the specified target object.
 The menu will appear in all views where an object of the specified type is selected.</description>
	</context>
	<context id="template_preference_page">
		<description>This template creates a page that is contributed to the Preferences.</description>
	</context>
	<context id="template_property_page">
		<description>This template adds a property page to a resource that matches the specified filter, and will appear in the Properties dialog for that resource.</description>
 	</context>
 	<context id="template_view">
 		<description>This template creates a workbench view and is contributed to the Workbench by creating a category.</description>
 	</context>
 	<context id="manifest_add_dependencies">
 		<description>This wizard allows you to add plug-ins as dependencies to your plug-in.
 Use the filter to accelerate your search for the plug-ins.</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
		<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
		<topic label="Creating a plug-in" href="guide/pde_creating.htm"/>
	</context>
	<context id="add_extensions_main">
		<description>This wizard allows you to add an extension to one of the available extension points.
 You can also create a working template extension from the list of available templates.</description>
 	</context>
 	<context id="add_extensions_schema_based">
 		<description>This wizard allows you to extend one of the available extension points.  To be able to extend an extension point, your plug-in has to import the plug-in where the point is declared.</description>
		<topic label="Dependencies page" href="guide/pde_manifest_dependencies.htm"/>
		<topic label="Extension point schema" href="guide/pde_schema.htm"/>
 	</context>
 	<context id="java_attribute_wizard_page">
 		<description>This wizard allows you to create a new Java class or select an existing one.</description>
 	</context>
 	<context id="feature_add_required_wizard">
 		<description>This wizard allows you to select the plug-ins that need to be present before the feature is installed.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	</context>
	<context id="feature_add_packaged_wizard">
		<description>This wizard allows you to select the plug-ins and fragments that are to be packaged in this feature.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	</context>
	<context id="feature_included_features_wizard">
		<description>This wizard allows you to select the features that are to be included in this feature.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	</context>
	<context id="feature_portability_wizard">
		<description>This wizard allows you to add constraints to ensure that your feature is not installed or shown in a context that does not match these constraints.</description>
		<topic label="Feature manifest editor" href="guide/pde_feature_manifest.htm"/>
	</context>		
	
	<context id="plugin_export_wizard" >
		<description>This wizard builds and exports the selected plug-ins and/or fragments into the specified location.</description>
		<topic label="Deploying a plug-in" href="guide/pde_deploy.htm"/>
	</context>
	<context id="feature_export_wizard">
		<description>This wizard builds and exports the selected features and the associated plug-ins into the specified location.</description>
		<topic label="Deploying a feature" href="guide/pde_feature_generating.htm"/>
	</context>
	
	<context id="plugins_container_page">
		<description>This page shows you the actual classpath entries that are managed by this dynamic classpath container. In case one of the library entries does not have source associated, you can add source by selecting 'Attach Source...' button.</description>
		<topic label="Build path computation" href="guide/pde_selfhosting_buildpath.htm" />
	</context>		
 		
<!-- Wizards -->

</contexts>