From 484c089036fdb58e41d783da03c58c49f657c250 Mon Sep 17 00:00:00 2001 From: Jesse Weinstein Date: Thu, 12 Sep 2013 17:26:29 -0400 Subject: [PATCH] [bug 417138] Various schema cleanups; English grammar fixes; adding translatable, identifier-type, etc. Change-Id: I1c10b4171bba0f8d64f41970eae1b2971bc53476 Signed-off-by: Jesse Weinstein Reviewed-on: https://git.eclipse.org/r/16395 Reviewed-by: Sergey Prigogin IP-Clean: Sergey Prigogin Tested-by: Sergey Prigogin --- .../schema/BinaryParser.exsd | 12 +- .../schema/CBuildConsole.exsd | 175 ++--- .../schema/CConfigurationDataProvider.exsd | 71 +- .../schema/CExtensionGeneric.exsd | 9 - core/org.eclipse.cdt.core/schema/CIndex.exsd | 625 +++++++++--------- .../org.eclipse.cdt.core/schema/CIndexer.exsd | 177 +++-- .../org.eclipse.cdt.core/schema/CProject.exsd | 180 ++--- .../schema/CProjectDescriptionStorage.exsd | 47 +- .../schema/CodeFormatter.exsd | 195 +++--- .../schema/EFSExtensionProvider.exsd | 68 +- .../schema/ErrorParser.exsd | 33 +- .../schema/LanguageSettingsProvider.exsd | 538 ++++++++------- .../schema/PathEntryContainerInitializer.exsd | 175 ++--- .../schema/ProcessList.exsd | 166 ++--- .../schema/RefreshExclusionFactory.exsd | 32 - .../schema/ScannerInfoProvider2.exsd | 45 +- .../schema/UNCPathConverter.exsd | 42 +- .../schema/externalSettingsProvider.exsd | 51 +- .../org.eclipse.cdt.core/schema/language.exsd | 10 - .../schema/projectConverter.exsd | 57 +- core/org.eclipse.cdt.core/schema/tagger.exsd | 10 - .../schema/templateAssociations.exsd | 40 +- .../schema/templateProcessTypes.exsd | 38 +- .../schema/templates.exsd | 477 +++++++------ 24 files changed, 1323 insertions(+), 1950 deletions(-) diff --git a/core/org.eclipse.cdt.core/schema/BinaryParser.exsd b/core/org.eclipse.cdt.core/schema/BinaryParser.exsd index e2697fdda10..bb91d19ae68 100644 --- a/core/org.eclipse.cdt.core/schema/BinaryParser.exsd +++ b/core/org.eclipse.cdt.core/schema/BinaryParser.exsd @@ -6,10 +6,9 @@ - This extension point is used to contribute a new Binary Parser to CDT. Binary parser analyses object/executable files to display their symbols and other information to a user. + This extension point is used to contribute a new Binary Parser to CDT. Binary Parsers analyse object or executable files in order to display their symbols and other information to users. - @@ -43,7 +42,6 @@ - @@ -52,7 +50,6 @@ - @@ -67,7 +64,6 @@ - @@ -106,7 +102,6 @@ - @@ -115,8 +110,6 @@ CDT 2.0 - - @@ -125,8 +118,6 @@ Plug-ins that want to extend this extension point must implement <samp>org.eclipse.cdt.core.IBinaryParser</samp> interface. - - @@ -139,5 +130,4 @@ which accompanies this distribution, and is available at<br/> http://www.eclipse.org/legal/epl-v10.html<br/> - diff --git a/core/org.eclipse.cdt.core/schema/CBuildConsole.exsd b/core/org.eclipse.cdt.core/schema/CBuildConsole.exsd index 217561eb74a..e98cae00a0d 100644 --- a/core/org.eclipse.cdt.core/schema/CBuildConsole.exsd +++ b/core/org.eclipse.cdt.core/schema/CBuildConsole.exsd @@ -1,109 +1,66 @@ - - - - - - - - - [Enter description of this extension point.] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - id of the build console, if not present then its the default console, (org.eclipse.cdt.ui provides the default console, so should never be specified). Builders can request a specific console via org.eclipse.cdt.core.CCorePlugin.getDefault().getConsole(String id); - - - - - - - Class which implents org.eclipse.cdt.core.resources.IConsole - - - - - - - - - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + id of the build console, if not present then its the default console, (org.eclipse.cdt.ui provides the default console, so should never be specified). Builders can request a specific console via org.eclipse.cdt.core.CCorePlugin.getDefault().getConsole(String id); + + + + + + + A class which implements org.eclipse.cdt.core.resources.IConsole + + + + + + + + + diff --git a/core/org.eclipse.cdt.core/schema/CConfigurationDataProvider.exsd b/core/org.eclipse.cdt.core/schema/CConfigurationDataProvider.exsd index ab41d6c737d..87ce1eb0f5b 100644 --- a/core/org.eclipse.cdt.core/schema/CConfigurationDataProvider.exsd +++ b/core/org.eclipse.cdt.core/schema/CConfigurationDataProvider.exsd @@ -1,16 +1,21 @@ - + - [Enter description of this extension point.] + Each time the Build Active configuration gets changed, the Project natures set gets adjusted by removing natures associated with the previously active configuration and adding natures associated with the new active configuration. +This allows adjusting the builders used with the project, etc. - + + + + + @@ -41,84 +46,32 @@ - - project nature ids associated with this provider. IDs are separated by the semicolon. -Each time the Build Active configuration gets changed, the project natures set gets adjusted by removing natures associated with the previously active configuration and adding natures associated with the new actove configuration. -This allows to adjust, e.g. the builders to be used with the project, etc. + Project nature IDs associated with this provider. IDs are separated by semicolons. - class implementing the org.eclipse.cdt.core.settings.model.extension.CConfigurationDataProvider + A class which extends org.eclipse.cdt.core.settings.model.extension.CConfigurationDataProvider - + - project nature ids to be unset for this provider. IDs are separated by the semicolon. -Each time the Build Active configuration gets changed, the project natures set gets adjusted by removing natures associated with the previously active configuration and natures conflicting for the new active configuration and adding natures associated with the new active configuration. - -This allows to adjust, e.g. the builders to be used with the project, etc. + Project nature IDs to be unset for this provider. IDs are separated by semicolons. - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - diff --git a/core/org.eclipse.cdt.core/schema/CExtensionGeneric.exsd b/core/org.eclipse.cdt.core/schema/CExtensionGeneric.exsd index 866b5cba73c..104771bc18a 100644 --- a/core/org.eclipse.cdt.core/schema/CExtensionGeneric.exsd +++ b/core/org.eclipse.cdt.core/schema/CExtensionGeneric.exsd @@ -9,7 +9,6 @@ Generic definition of extension point used by ICConfigExtensionReference. This definition is for a family of extension points not for any specific one. - @@ -43,7 +42,6 @@ - @@ -51,7 +49,6 @@ - @@ -66,11 +63,6 @@ - - - - - @@ -83,5 +75,4 @@ which accompanies this distribution, and is available at<br/> http://www.eclipse.org/legal/epl-v10.html<br/> - diff --git a/core/org.eclipse.cdt.core/schema/CIndex.exsd b/core/org.eclipse.cdt.core/schema/CIndex.exsd index 67a8dc28b20..84ab5fab065 100644 --- a/core/org.eclipse.cdt.core/schema/CIndex.exsd +++ b/core/org.eclipse.cdt.core/schema/CIndex.exsd @@ -1,322 +1,303 @@ - - - - - - - - - This extension point groups extensions to the index functionality in CDT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - <h2>ExportProjectProvider</h2> -<p> -This subelement of CIndex allows contribution of alternate IExportProjectProvider implementations. These can then be referenced by fully qualified class name in the command line tool (see option -pprovider). -<p> -<b>Invoking the application as a headless application</b> - -This example ant file shows how to invoke the tool headlessly, the same approach would work from a shell or batch file. - -<pre> -<project name="Generate PDOM" default="generate"> - <target name="generate"> - <!-- This script shows how to invoke the default project provider (ExternalExportProjectProvider) --> - <property name="pprovider" value="org.eclipse.cdt.core.index.export.ExternalExportProjectProvider"/> - <property name="target" value="C:\ExportedPDOMs\acmeSDK_2_5.pdom"/> <!-- Where the output pdom is to go --> - <property name="source" value="E:\AcmeSDK\v2.5\inc"/> <!-- e.g. the directory to source content from --> - <property name="id" value="com.acme.mysdk.v2.5"/> <!-- the id to store in the generate pdom --> - - <property name="eclipse.home" value="C:\eclipse"/> <!-- e.g. The eclipse installation to use. This installation must contain CDT 4.0+ plugins --> - - <java classname="org.eclipse.equinox.launcher.Main"> - <classpath> - <fileset dir="${eclipse.home}/plugins"> - <include name="*equinox.launcher*.jar"/> - </fileset> - </classpath> - <arg value="-nosplash"/> - <arg value="-exitdata"/> - <arg value="-application"/><arg value="org.eclipse.cdt.core.GeneratePDOM"/> - <arg value="-pprovider"/><arg value="${pprovider}"/> - <arg value="-source"/><arg value="${source}"/> - <arg value="-target"/><arg value="${target}"/> - <arg value="-id"/><arg value="${id}"/> - </java> - </target> -</project> -</pre> -<p> -<b>Invoking the tool via an Eclipse Launch Configuration</b> -<p> -Specify "org.eclipse.cdt.core.GeneratePDOM" as the application to launch -<p> -In the Argument tabs provide (for example) - -target C:\ExportedPDOMs\acmeSDK_2_5.pdom -source E:\AcmeSDK\v2.5\inc -include E:\this.h -id com.acme.mysdk.v2.5 -<p> - - - - - - - the fully qualified name of the IExportProjectProvider implementation to register - - - - - - - - - - - - - <h2>ReadOnlyPDOMProvider</h2> -<p> -This subelement of CIndex allows ISVs to contribute read-only prebuilt PDOM files to the CDT Index. The only information needed is the fully qualified class name of an implementatin of org.eclipse.cdt.core.index.IOfflinePDOMProvider. This implementation will be consulted during the eclipse session for the appropriate read-only content to make add to the logical index. The logical index is accessible via the org.eclipse.core.index.IIndex API. - - An example of contributing a prebuilt read-only pdom: -<pre> -<CIndex> - <ReadOnlyPDOMProvider class="com.acme.ide.index.AcmeSDKProvider"/> -</CIndex> -</pre> - -and the corresponding implementation - -<pre> -package com.acme.ide.index.sdk; - -import org.eclipse.core.index.provider.IReadOnlyPDOMProvider; -import org.eclipse.core.index.provider.IPDOMDescriptor; -import org.eclipse.core.index.IIndexLocationConverter; -import org.eclipse.core.index.URIRelativeLocationConverter; - -public class AcmeSDKProvider implements IReadOnlyPDOMProvider { - public boolean providesFor(ICProject project) { - // e.g. decide by looking for acme project nature - return AcmeNature.isAcmeProject(project); - } - - public IPDOMDescriptor[] getDescriptors(ICConfigurationDescription config) { - final IPath sdkBase = AcmeSDKAPI.getSDKBase(config); - return new IPDOMDescriptor[] { new IPDOMDescriptor() { - public IIndexLocationConverter getIndexLocationConverter() { - return new URIRelativeLocationConverter(URIUtil.toURI(sdkBase)); - } - public IPath getLocation() { - IPath path = sdkBase.append(AcmeSDKAPI.getPrebuiltPDOMFilename(config)); - return path; - } - }}; - } -} -</pre> - - - - - - - - - - The fully qualified name of the IReadOnlyPDOMProvider implementation to register - - - - - - - - - - - - - <h2>ReadOnlyIndexFragmentProvider</h2> -<p> -This subelement of CIndex allows ISVs to contribute read-only index fragments to the CDT Index. This extension point imposes no limitations on how the index information is collected and stored. The index fragments may, for example, be based on data dynamically fetched from a remote server. -<p> -The only information needed for this extension point is the fully qualified name of a class implementing the org.eclipse.cdt.core.index.IIndexFragmentProvider interface. This class will be consulted during the eclipse session for the appropriate read-only content to add to the logical index. The logical index is accessible via the org.eclipse.core.index.IIndex API. - - - - - - - - - - The fully qualified name of a class implementing IIndexFragmentProvider interface. - - - - - - - - - - - - - Defines for which tools the fragment provider shall be used. - - - - - - - Whether the fragment provider shall be used for performing 'Open Declaration' and 'Open Element'. - - - - - - - Whether the fragment provider shall be used for performing content-assist. - - - - - - - Whether the fragment provider shall be used for performing 'Add Import'. - - - - - - - Whether the fragment provider shall be used for populating the call hierarchy. - - - - - - - Whether the fragment provider shall be used for populating the type hierarchy. - - - - - - - Whether the fragment provider shall be used for populating the include browser. - - - - - - - Whether the fragment provider shall be used for C/C++ searches. - - - - - - - Whether the fragment provider shall be used for C/C++ editor. - - - - - - - - - - - - Index content provided by ISVs under this extension point will be accessible via the logical index org.eclipse.core.index.IIndex API - -For export functionality, see package org.eclipse.cdt.core.index.export - - - - - - - - - 4.0 - - - - - - - - - See subelement documentation - - - - - - - - - See subelement documentation - - - - - - - - - Copyright (c) 2007, 2011 Symbian Software Systems and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - - - - + + + + + + + + + This extension point groups extensions to the index functionality in CDT + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + <h2>ExportProjectProvider</h2> +<p> +This subelement of CIndex allows contribution of alternate IExportProjectProvider implementations. These can then be referenced by fully qualified class name in the command line tool (see option -pprovider). +<p> +<b>Invoking the application as a headless application</b> +This example ant file shows how to invoke the tool headlessly, the same approach would work from a shell or batch file. +<pre> +<project name="Generate PDOM" default="generate"> + <target name="generate"> + <!-- This script shows how to invoke the default project provider (ExternalExportProjectProvider) --> + <property name="pprovider" value="org.eclipse.cdt.core.index.export.ExternalExportProjectProvider"/> + <property name="target" value="C:\ExportedPDOMs\acmeSDK_2_5.pdom"/> <!-- Where the output pdom is to go --> + <property name="source" value="E:\AcmeSDK\v2.5\inc"/> <!-- e.g. the directory to source content from --> + <property name="id" value="com.acme.mysdk.v2.5"/> <!-- the id to store in the generate pdom --> + + <property name="eclipse.home" value="C:\eclipse"/> <!-- e.g. The eclipse installation to use. This installation must contain CDT 4.0+ plugins --> + + <java classname="org.eclipse.equinox.launcher.Main"> + <classpath> + <fileset dir="${eclipse.home}/plugins"> + <include name="*equinox.launcher*.jar"/> + </fileset> + </classpath> + <arg value="-nosplash"/> + <arg value="-exitdata"/> + <arg value="-application"/><arg value="org.eclipse.cdt.core.GeneratePDOM"/> + <arg value="-pprovider"/><arg value="${pprovider}"/> + <arg value="-source"/><arg value="${source}"/> + <arg value="-target"/><arg value="${target}"/> + <arg value="-id"/><arg value="${id}"/> + </java> + </target> +</project> +</pre> +<p> +<b>Invoking the tool via an Eclipse Launch Configuration</b> +<p> +Specify "org.eclipse.cdt.core.GeneratePDOM" as the application to launch +<p> +In the Argument tabs provide (for example) + -target C:\ExportedPDOMs\acmeSDK_2_5.pdom -source E:\AcmeSDK\v2.5\inc -include E:\this.h -id com.acme.mysdk.v2.5 +<p> + + + + + + + The fully qualified name of the IExportProjectProvider implementation to register. + + + + + + + + + + + + <h2>ReadOnlyPDOMProvider</h2> +<p> +This subelement of CIndex allows ISVs to contribute read-only prebuilt PDOM files to the CDT Index. The only information needed is the fully qualified class name of an implementatin of org.eclipse.cdt.core.index.IOfflinePDOMProvider. This implementation will be consulted during the eclipse session for the appropriate read-only content to make add to the logical index. The logical index is accessible via the org.eclipse.core.index.IIndex API. + + An example of contributing a prebuilt read-only pdom: +<pre> +<CIndex> + <ReadOnlyPDOMProvider class="com.acme.ide.index.AcmeSDKProvider"/> +</CIndex> +</pre> +and the corresponding implementation +<pre> +package com.acme.ide.index.sdk; +import org.eclipse.core.index.provider.IReadOnlyPDOMProvider; +import org.eclipse.core.index.provider.IPDOMDescriptor; +import org.eclipse.core.index.IIndexLocationConverter; +import org.eclipse.core.index.URIRelativeLocationConverter; +public class AcmeSDKProvider implements IReadOnlyPDOMProvider { + public boolean providesFor(ICProject project) { + // e.g. decide by looking for acme project nature + return AcmeNature.isAcmeProject(project); + } + public IPDOMDescriptor[] getDescriptors(ICConfigurationDescription config) { + final IPath sdkBase = AcmeSDKAPI.getSDKBase(config); + return new IPDOMDescriptor[] { new IPDOMDescriptor() { + public IIndexLocationConverter getIndexLocationConverter() { + return new URIRelativeLocationConverter(URIUtil.toURI(sdkBase)); + } + public IPath getLocation() { + IPath path = sdkBase.append(AcmeSDKAPI.getPrebuiltPDOMFilename(config)); + return path; + } + }}; + } +} +</pre> + + + + + + + + + + The fully qualified name of the IReadOnlyPDOMProvider implementation to register. + + + + + + + + + + + + <h2>ReadOnlyIndexFragmentProvider</h2> +<p> +This subelement of CIndex allows ISVs to contribute read-only index fragments to the CDT Index. This extension point imposes no limitations on how the index information is collected and stored. The index fragments may, for example, be based on data dynamically fetched from a remote server. +<p> +The only information needed for this extension point is the fully qualified name of a class implementing the org.eclipse.cdt.core.index.IIndexFragmentProvider interface. This class will be consulted during the eclipse session for the appropriate read-only content to add to the logical index. The logical index is accessible via the org.eclipse.core.index.IIndex API. + + + + + + + + + + The fully qualified name of a class implementing IIndexFragmentProvider. + + + + + + + + + + + + Defines for which tools the fragment provider shall be used. + + + + + + + Whether the fragment provider shall be used for performing 'Open Declaration' and 'Open Element'. + + + + + + + Whether the fragment provider shall be used for performing content-assist. + + + + + + + Whether the fragment provider shall be used for performing 'Add Import'. + + + + + + + Whether the fragment provider shall be used for populating the call hierarchy. + + + + + + + Whether the fragment provider shall be used for populating the type hierarchy. + + + + + + + Whether the fragment provider shall be used for populating the include browser. + + + + + + + Whether the fragment provider shall be used for C/C++ searches. + + + + + + + Whether the fragment provider shall be used for C/C++ editor. + + + + + + + + + + + 4.0 + + + + + + + + See subelement documentation + + + + + + + + See subelement documentation + + + + + + + + Copyright (c) 2007, 2011 Symbian Software Systems and others. +All rights reserved. This program and the accompanying materials +are made available under the terms of the Eclipse Public License v1.0 +which accompanies this distribution, and is available at +http://www.eclipse.org/legal/epl-v10.html + + + + + + + + Index content provided by ISVs under this extension point will be accessible via the logical index org.eclipse.core.index.IIndex API +For export functionality, see package org.eclipse.cdt.core.index.export + + + diff --git a/core/org.eclipse.cdt.core/schema/CIndexer.exsd b/core/org.eclipse.cdt.core/schema/CIndexer.exsd index eb1304c2def..fe2be7f4dce 100644 --- a/core/org.eclipse.cdt.core/schema/CIndexer.exsd +++ b/core/org.eclipse.cdt.core/schema/CIndexer.exsd @@ -1,102 +1,75 @@ - - - - - - - - - This extension point is used to contribute a new Indexer to the CDT. This indexer can choose to receive event notification from the index manager. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - CDT 3.0 - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - Plug-ins that want to extend this extension point must implement <samp>org.eclipse.cdt.core.index.IIndexer</samp> interface. - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - - + + + + + + + + + This extension point is used to contribute a new Indexer to the CDT. This indexer can choose to receive event notification from the index manager. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Plug-ins that want to extend this extension point must implement <samp>org.eclipse.cdt.core.index.IIndexer</samp> interface. + + + + + + + + CDT 3.0 + + + diff --git a/core/org.eclipse.cdt.core/schema/CProject.exsd b/core/org.eclipse.cdt.core/schema/CProject.exsd index d8d0cce7d9e..b54da506e9c 100644 --- a/core/org.eclipse.cdt.core/schema/CProject.exsd +++ b/core/org.eclipse.cdt.core/schema/CProject.exsd @@ -1,107 +1,73 @@ - - - - - - - - - [Enter description of this extension point] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Class which implements org.eclipse.cdt.core.ICOwner - - - - - - - - - - This is a nature ID which the owner has. This is used to restore a ICDescriptor which has been deleted. If this is not provided the descriptor will be restore with no owner. A project with multiple natures will use the first matching nature searched in the reverse order in the Project Description. - - - - - - - - - - - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Class which implements org.eclipse.cdt.core.ICOwner + + + + + + + + + + This is a nature ID which the owner has. This is used to restore a ICDescriptor which has been deleted. If this is not provided the descriptor will be restored without an owner. A project with multiple natures will use the first matching nature searched in the reverse order in the Project Description. + + + + + + + + + + + + + diff --git a/core/org.eclipse.cdt.core/schema/CProjectDescriptionStorage.exsd b/core/org.eclipse.cdt.core/schema/CProjectDescriptionStorage.exsd index fbf9952a7c8..0d0a1f1ea7d 100644 --- a/core/org.eclipse.cdt.core/schema/CProjectDescriptionStorage.exsd +++ b/core/org.eclipse.cdt.core/schema/CProjectDescriptionStorage.exsd @@ -2,19 +2,18 @@ - + - + This extension point allows contributors to provide their own implementation of the CProjectDescriptionStorage backing store. - - + - + @@ -39,14 +38,13 @@ - + - + - @@ -59,9 +57,9 @@ A factory class that implements ICProjectDescriptionStorageType to create AbstractCProjectDescriptionStorages for given IProjects - + - + @@ -69,6 +67,9 @@ Id of this particular project description storage type + + + @@ -100,41 +101,27 @@ This String value must be compatible with org.eclipse.osgi.framework.version Human readable name of this project description type - + - + - - + - + 6.0 - - - - - - - [Enter API information here.] - - - - - + - + See the example XmlProjectDescriptionStorage & XmlProjectDescriptionStorage2 in this plugin - - diff --git a/core/org.eclipse.cdt.core/schema/CodeFormatter.exsd b/core/org.eclipse.cdt.core/schema/CodeFormatter.exsd index 3886794bb89..6fcee028a10 100644 --- a/core/org.eclipse.cdt.core/schema/CodeFormatter.exsd +++ b/core/org.eclipse.cdt.core/schema/CodeFormatter.exsd @@ -1,116 +1,79 @@ - - - - - - - - - [Enter description of this extension point.] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A unique name that will be used to reference this code formatter - - - - - - - A translatable name that will be used for presenting this formatter in the UI. - - - - - - - a fully qualified name of the Java class that implements <samp>org.eclipse.cdt.core.formatter.CodeFormatter</samp> abstract class. - - - - - - - - - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A unique name that will be used to reference this code formatter + + + + + + + + + + A translatable name that will be used for presenting this formatter in the UI. + + + + + + + + + + A fully qualified name of the Java class that extends the <samp>org.eclipse.cdt.core.formatter.CodeFormatter</samp> abstract class. + + + + + + + + + diff --git a/core/org.eclipse.cdt.core/schema/EFSExtensionProvider.exsd b/core/org.eclipse.cdt.core/schema/EFSExtensionProvider.exsd index 0107d4bd39c..7d641dca34a 100644 --- a/core/org.eclipse.cdt.core/schema/EFSExtensionProvider.exsd +++ b/core/org.eclipse.cdt.core/schema/EFSExtensionProvider.exsd @@ -9,34 +9,6 @@ This extension point allows one to contribute a class that provides supplementary support for an EFS filesystem in the form of a provider of a set of utility methods. In particular, the class can extract meaningful information from the filesystem and its resources, and provide useful operations relating to such resources. - - - - - An instance of an EFS Extension Provider. EFS Extension Providers are mapped to a URI scheme corresponding to an EFS filesystem for which they provide support. These extensions are consulted by CDT in order to extract path information from the filesystem and manipulate filesystem resources. - - - - - - - The URI scheme of an EFS filesystem this utility provides support for. - - - - - - - Java class which extends from org.eclipse.cdt.core.EFSFileSystemSupplementarySupportProvider to provide support for the filesystem. - - - - - - - - - @@ -73,7 +45,32 @@ - + + + + An instance of an EFS Extension Provider. EFS Extension Providers are mapped to a URI scheme corresponding to an EFS filesystem for which they provide support. These extensions are consulted by CDT in order to extract path information from the filesystem and manipulate filesystem resources. + + + + + + + The URI scheme of an EFS filesystem this utility provides support for. + + + + + + + Java class which extends from org.eclipse.cdt.core.EFSFileSystemSupplementarySupportProvider to provide support for the filesystem. + + + + + + + + @@ -82,17 +79,6 @@ 5.2 - - - - - - - - [Enter API information here.] - - - @@ -101,6 +87,4 @@ A default implementation is supplied by org.eclipse.cdt.core.EFSFileSystemUtilityProvider that assumes that URIs for the given filesystem map directly to resources in the physical filesystem, and that the path component of the URI is a direct representation of the absolute path to the file in the physical filesystem. Clients can extend this implementation and override its behaviour as needed. - - diff --git a/core/org.eclipse.cdt.core/schema/ErrorParser.exsd b/core/org.eclipse.cdt.core/schema/ErrorParser.exsd index 5067911232e..ff1e0e837dd 100644 --- a/core/org.eclipse.cdt.core/schema/ErrorParser.exsd +++ b/core/org.eclipse.cdt.core/schema/ErrorParser.exsd @@ -9,7 +9,6 @@ This extension point is used to contribute a new Error Parser. A Error Parser is used to parse errors/warnings/info from build output and populate Problems View with them. - @@ -43,7 +42,6 @@ - @@ -55,6 +53,9 @@ ID of the error parser. If attribute is missing error parser ID is constructed appending Simple ID of extension to plugin ID. + + + @@ -62,12 +63,15 @@ Name of the error parser. If this attribute is missing extension name is taken. + + + - a fully qualified name of the Java class that implements <samp>org.eclipse.cdt.core.IErrorParser</samp> interface. + a fully qualified name of the Java class that implements <samp>org.eclipse.cdt.core.IErrorParser</samp> @@ -76,7 +80,6 @@ - @@ -87,7 +90,7 @@ - Attribute "severity" specifies which severity should be used to display the marker in Problems View. There are 3 levels of severity, "Error", "Warning" and "Info". "Ignore" lets stop evaluating the line by the rest of patterns without showing up in Problems View. + This attribute specifies which severity should be used to display the marker in Problems View. There are 3 levels of severity, "Error", "Warning" and "Info". The forth option, "Ignore" tells the system to stop checking the line against the other patterns without causing it to show up in the Problems View. @@ -106,7 +109,7 @@ - Java regular expression to define capturing groups for file-expr, line-expr and description-expr. + Java regular expression which defines capturing groups for file-expr, line-expr and description-expr. @@ -141,20 +144,17 @@ - The attribute defines if a line matched by the pattern is prevented or allowed to be processed by the rest of patterns. "No" allows several patterns to evaluate one line. + The attribute defines if a line matched by the pattern is prevented or allowed to be processed by the rest of the patterns. "false" allows several patterns to evaluate the same line. - - Use this element to specify the context where an error parser can be used. If none is specified, a default context type will be "build". - -An example of context type is "build". Only error parsers in this context are used to parse build output. You can see these error parsers in the "C/C++" > "Build" > "Settings" preference page. - + Use this element to specify the context where an error parser can be used. If none is specified, the default context type will be "build". +An example of a context type is "build". Only error parsers in this context are used to parse build output. You can see these error parsers in the "C/C++" > "Build" > "Settings" preference page. An error parser can be assigned to more than one context type. Clients contributing error parsers are free to define their own context types. @@ -168,7 +168,6 @@ An error parser can be assigned to more than one context type. Clients contribut - @@ -177,14 +176,12 @@ An error parser can be assigned to more than one context type. Clients contribut CDT 1.2 - - <br/> -package org.eclipse.cdt.example.errorparser;<br/> + package org.eclipse.cdt.example.errorparser;<br/> <br/> import org.eclipse.cdt.core.IMarkerGenerator;<br/> import org.eclipse.cdt.core.errorparsers.AbstractErrorParser;<br/> @@ -209,7 +206,6 @@ public class SampleErrorParser extends AbstractErrorParser {<br/> }<br/> - @@ -223,7 +219,6 @@ Another good choice is to extend <samp>org.eclipse.cdt.core.errorparsers.A ErrorParsers dealing with multi-line messages should implement <samp>org.eclipse.cdt.core.IErrorParser2</samp> interface. - @@ -232,7 +227,6 @@ ErrorParsers dealing with multi-line messages should implement <samp>org.e For another example of implementation see org.eclipse.cdt.internal.errorparsers.GCCErrorParser - @@ -245,5 +239,4 @@ which accompanies this distribution, and is available at<br/> http://www.eclipse.org/legal/epl-v10.html<br/> - diff --git a/core/org.eclipse.cdt.core/schema/LanguageSettingsProvider.exsd b/core/org.eclipse.cdt.core/schema/LanguageSettingsProvider.exsd index 692e5d9098d..ab7adac15c2 100644 --- a/core/org.eclipse.cdt.core/schema/LanguageSettingsProvider.exsd +++ b/core/org.eclipse.cdt.core/schema/LanguageSettingsProvider.exsd @@ -1,280 +1,258 @@ - - - - - - - - - This extension point is used to contribute a new Language Settings Provider. A Language Settings Provider is used to get additions to compiler options such as include paths (-I) or preprocessor defines (-D) and others into the project model. - - - - - - - - - - This extension point is used to contribute a new Language Settings Provider. A Language Settings Provider is used to get additions to compiler options such as include paths (-I) or preprocessor defines (-D) and others into the project model. - - - - - - - - - - - - - - - - - ID of the extension point, not used - - - - - - - Name of the extension point, not used - - - - - - - - - - - - - The definition of a language settings provider. - - - - - - - - - - - A fully qualified name of the Java class that implements <samp>org.eclipse.cdt.core.language.settings.providers</samp> interface. If empty, <samp>org.eclipse.cdt.core.language.settings.providers.LanguageSettingsBaseProvider</samp> is used by default which provides basic functionality defined by this extension point.<br> -In case the provider ever needs to be non-shared, set per project/configuration, or editable in UI - the provider must implement <samp>org.eclipse.cdt.core.language.settings.providers.ILanguageSettingsEditableProvider</samp>. There is a generic implementation <samp>org.eclipse.cdt.core.language.settings.providers.LanguageSettingsGenericProvider</samp> that can be used in most cases.<br> -If there is a need to configure a provider in more deliberate way, attribute <samp>parameter</samp> could be used in a class extending <samp>LanguageSettingsBaseProvider</samp>.<br> -Default constructor (constructor without arguments) of this class must be public and the package be exported in order to be able to instantiate via extension point. - - - - - - - - - - Unique ID of the provider. - - - - - - - Name of the provider. This name will be presented to a user in UI. - - - - - - - A custom parameter to initialize provider. For example, used to deliver command for GCCBuiltinSpecsDetector. - - - - - - - A flag indicating that the provider should be owned by a configuration rather than be global in workspace and shared between projects (when the choice has not been indicated yet by other means). This preference is consulted in order to initially set the "shared" attribute, for example when a user adds a provider from the list of extension providers. -The value "true" of this attribute is meaningful only for providers capable of being non-shared, i.e. providers extending ILanguageSettingsEditableProvider. - - - - - - - - - - The definition of language scope. Includes the list of language ID this provider is applicable to. If a language scope is not present, the provider will provide for any language. - - - - - - - ID of the language for which this provider provides the entries. As an example, those are languages contributed by CDT (see extension org.eclipse.cdt.core.language): -<p>- "<samp>org.eclipse.cdt.core.gcc</samp>" for C,</p> -<p>- "<samp>org.eclipse.cdt.core.g++</samp>" for C++.</p> - - - - - - - - - - The Language Settings Entries used to provide additions to compiler options such as include paths (-I) or preprocessor defines (-D) and others into the project model. - - - - - - - - - - Kind of language settings entry which maps to compiler options. For example, following mapping is used for gcc options: - -<br>"<samp>-I</samp>" : includePath -<br>"<samp>-D</samp>" : macro -<br>"<samp>-include</samp>" : includeFile -<br>"<samp>-L</samp>" : libraryPath -<br>"<samp>-l</samp>" : libraryFile -<br>"<samp>-imacros</samp>" : macroFile - - - - - - - - - - - - - - - - - - - - - - - "name" attribute maps to path for the entries representing a path to a folder or file and to name for <samp>macro</samp> kind representing name-value pair. For example: -<br>"<samp>/usr/include/</samp>" -<br>"<samp>MACRO</samp>" (for <samp>#define MACRO value</samp>) -<br>Note that relative paths are treated as rooted in build working directory (when applicable). - - - - - - - "value" attribute is used for <samp>macro</samp> kind representing name-value pair only. It is not used for the entries representing a path. For example: -<br>"<samp>value</samp>" (for <samp>#define MACRO value</samp>) - - - - - - - - - - Combination of flags for the entry. - - - - - - - A value of the flag. Corresponds to <samp>ICSettingEntry</samp> flags, see JavaDoc there for more details. Here is an excerpt from the Javadoc for the flags intended to be used with this extension point (the others might be not supported): - <br>- <samp>BUILTIN</samp> : Indicates settings built in a tool (compiler) itself. That kind of settings are not passed as options to a compiler but indexer or other clients might need them. - <br>- <samp>LOCAL</samp> : Applicable for <samp>includePath</samp> only which could be local (#include "...") or system (#include <...>). If an <samp>includePath</samp> is not marked as <samp>LOCAL</samp> it is treated as system. - <br>- <samp>RESOLVED</samp> : Indicates that the entries do not need to be resolved such as expansion of environment variables, normalizing the path against build working directory etc. - <br>- <samp>VALUE_WORKSPACE_PATH</samp> : is used to indicate that the entry is a resource managed by eclipse in the workspace. The path is rooted in the workspace root. - <br>- <samp>UNDEFINED</samp> : indicates that the entry should not be defined, corresponds to <samp>-U</samp> option of gcc compiler. If this flag is defined it will negate entries with the same name (and kind) for all providers down the list. - <br>- <samp>EXPORTED</samp> : indicates that the entry is exported to referencing projects. It will be passed to the projects configurations referencing the configuration the entry belongs to. - - - - - - - - - - - - - - - - - - - - - - - - - - - - CDT 8.1 - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - Plug-ins that want to extend this extension point must implement <samp>org.eclipse.cdt.core.language.settings.providers.ILanguageSettingsProvider</samp> interface. -<br/> -For those cases where contributed settings entries (representing the compiler options) are not changed dynamically it is sufficient to configure existing class LanguageSettingsBaseProvider which is provided by default. -<br/> - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - Copyright (c) 2009, 2013 Andrew Gvozdev and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - - - - + + + + + + + + + This extension point is used to contribute a new Language Settings Provider. A Language Settings Provider is used to get additions to compiler options such as include paths (-I) or preprocessor defines (-D) and others into the project model. + + + + + + + + + This extension point is used to contribute a new Language Settings Provider. A Language Settings Provider is used to get additions to compiler options such as include paths (-I) or preprocessor defines (-D) and others into the project model. + + + + + + + + + + + + + + + + + ID of the extension point, not used + + + + + + + Name of the extension point, not used + + + + + + + + + + + + The definition of a language settings provider. + + + + + + + + + + + A fully qualified name of the Java class that implements <samp>org.eclipse.cdt.core.language.settings.providers</samp> interface. If empty, <samp>org.eclipse.cdt.core.language.settings.providers.LanguageSettingsBaseProvider</samp> is used by default which provides basic functionality defined by this extension point.<br> +In case the provider ever needs to be non-shared, set per project/configuration, or editable in UI - the provider must implement <samp>org.eclipse.cdt.core.language.settings.providers.ILanguageSettingsEditableProvider</samp>. There is a generic implementation <samp>org.eclipse.cdt.core.language.settings.providers.LanguageSettingsGenericProvider</samp> that can be used in most cases.<br> +If there is a need to configure a provider in more deliberate way, attribute <samp>parameter</samp> could be used in a class extending <samp>LanguageSettingsBaseProvider</samp>.<br> +Default constructor (constructor without arguments) of this class must be public and the package be exported in order to be able to instantiate via extension point. + + + + + + + + + + Unique ID of the provider. + + + + + + + + + + Name of the provider. This name will be presented to a user in UI. + + + + + + + + + + A custom parameter to initialize provider. For example, used to deliver command for GCCBuiltinSpecsDetector. + + + + + + + A flag indicating that the provider should be owned by a configuration rather than be global in workspace and shared between projects (when the choice has not been indicated yet by other means). This preference is consulted in order to initially set the "shared" attribute, for example when a user adds a provider from the list of extension providers. +The value "true" of this attribute is meaningful only for providers capable of being non-shared, i.e. providers extending ILanguageSettingsEditableProvider. + + + + + + + + + The definition of language scope. Includes the list of language ID this provider is applicable to. If a language scope is not present, the provider will provide for any language. + + + + + + + ID of the language for which this provider provides the entries. As an example, those are languages contributed by CDT (see extension org.eclipse.cdt.core.language): +<p>- "<samp>org.eclipse.cdt.core.gcc</samp>" for C,</p> +<p>- "<samp>org.eclipse.cdt.core.g++</samp>" for C++.</p> + + + + + + + + + The Language Settings Entries used to provide additions to compiler options such as include paths (-I) or preprocessor defines (-D) and others into the project model. + + + + + + + + + + Kind of language settings entry which maps to compiler options. For example, following mapping is used for gcc options: +<br>"<samp>-I</samp>" : includePath +<br>"<samp>-D</samp>" : macro +<br>"<samp>-include</samp>" : includeFile +<br>"<samp>-L</samp>" : libraryPath +<br>"<samp>-l</samp>" : libraryFile +<br>"<samp>-imacros</samp>" : macroFile + + + + + + + + + + + + + + + + + + + + + + + "name" attribute maps to path for the entries representing a path to a folder or file and to name for <samp>macro</samp> kind representing name-value pair. For example: +<br>"<samp>/usr/include/</samp>" +<br>"<samp>MACRO</samp>" (for <samp>#define MACRO value</samp>) +<br>Note that relative paths are treated as rooted in build working directory (when applicable). + + + + + + + "value" attribute is used for <samp>macro</samp> kind representing name-value pair only. It is not used for the entries representing a path. For example: +<br>"<samp>value</samp>" (for <samp>#define MACRO value</samp>) + + + + + + + + + Combination of flags for the entry. + + + + + + + A value of the flag. Corresponds to <samp>ICSettingEntry</samp> flags, see JavaDoc there for more details. Here is an excerpt from the Javadoc for the flags intended to be used with this extension point (the others might be not supported): + <br>- <samp>BUILTIN</samp> : Indicates settings built in a tool (compiler) itself. That kind of settings are not passed as options to a compiler but indexer or other clients might need them. + <br>- <samp>LOCAL</samp> : Applicable for <samp>includePath</samp> only which could be local (#include "...") or system (#include <...>). If an <samp>includePath</samp> is not marked as <samp>LOCAL</samp> it is treated as system. + <br>- <samp>RESOLVED</samp> : Indicates that the entries do not need to be resolved such as expansion of environment variables, normalizing the path against build working directory etc. + <br>- <samp>VALUE_WORKSPACE_PATH</samp> : is used to indicate that the entry is a resource managed by eclipse in the workspace. The path is rooted in the workspace root. + <br>- <samp>UNDEFINED</samp> : indicates that the entry should not be defined, corresponds to <samp>-U</samp> option of gcc compiler. If this flag is defined it will negate entries with the same name (and kind) for all providers down the list. + <br>- <samp>EXPORTED</samp> : indicates that the entry is exported to referencing projects. It will be passed to the projects configurations referencing the configuration the entry belongs to. + + + + + + + + + + + + + + + + + + + + + + + + + + + CDT 8.1 + + + + + + + + Plug-ins that want to extend this extension point must implement <samp>org.eclipse.cdt.core.language.settings.providers.ILanguageSettingsProvider</samp> interface. +<br/> +For those cases where contributed settings entries (representing the compiler options) are not changed dynamically it is sufficient to configure existing class LanguageSettingsBaseProvider which is provided by default. +<br/> + + + + + + + + Copyright (c) 2009, 2013 Andrew Gvozdev and others. +All rights reserved. This program and the accompanying materials +are made available under the terms of the Eclipse Public License v1.0 +which accompanies this distribution, and is available at +http://www.eclipse.org/legal/epl-v10.html + + + diff --git a/core/org.eclipse.cdt.core/schema/PathEntryContainerInitializer.exsd b/core/org.eclipse.cdt.core/schema/PathEntryContainerInitializer.exsd index dfbb34ae616..7ba6fe1fa97 100644 --- a/core/org.eclipse.cdt.core/schema/PathEntryContainerInitializer.exsd +++ b/core/org.eclipse.cdt.core/schema/PathEntryContainerInitializer.exsd @@ -1,109 +1,66 @@ - - - - - - - - - [Enter description of this extension point.] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/core/org.eclipse.cdt.core/schema/ProcessList.exsd b/core/org.eclipse.cdt.core/schema/ProcessList.exsd index f0de8fa1de6..7864c473f5e 100644 --- a/core/org.eclipse.cdt.core/schema/ProcessList.exsd +++ b/core/org.eclipse.cdt.core/schema/ProcessList.exsd @@ -1,100 +1,66 @@ - - - - - - - - - [Enter description of this extension point] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/core/org.eclipse.cdt.core/schema/RefreshExclusionFactory.exsd b/core/org.eclipse.cdt.core/schema/RefreshExclusionFactory.exsd index c683ea2f9bc..204a1501a3d 100644 --- a/core/org.eclipse.cdt.core/schema/RefreshExclusionFactory.exsd +++ b/core/org.eclipse.cdt.core/schema/RefreshExclusionFactory.exsd @@ -9,7 +9,6 @@ This extension point allows ISVs to contribute factory classes that know how to instantiate a given type of RefreshExclusion. Usage of this extension point is mandatory when contributing new types of RefreshExclusions as otherwise CDT cannot instantiate the proper exclusions when loading persisted settings relating to the refresh policy for a given project. - @@ -46,7 +45,6 @@ - @@ -81,7 +79,6 @@ - @@ -90,34 +87,6 @@ 5.3.0 - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - @@ -130,5 +99,4 @@ this distribution, and is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a> - diff --git a/core/org.eclipse.cdt.core/schema/ScannerInfoProvider2.exsd b/core/org.eclipse.cdt.core/schema/ScannerInfoProvider2.exsd index ad56496eab2..7ab05e8cb71 100644 --- a/core/org.eclipse.cdt.core/schema/ScannerInfoProvider2.exsd +++ b/core/org.eclipse.cdt.core/schema/ScannerInfoProvider2.exsd @@ -6,10 +6,9 @@ - [Enter description of this extension point.] + - @@ -46,7 +45,6 @@ - @@ -64,46 +62,11 @@ The id of the build command this scanner info provider provides for. + + + - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - diff --git a/core/org.eclipse.cdt.core/schema/UNCPathConverter.exsd b/core/org.eclipse.cdt.core/schema/UNCPathConverter.exsd index 25db7597e8f..e808a49fd24 100644 --- a/core/org.eclipse.cdt.core/schema/UNCPathConverter.exsd +++ b/core/org.eclipse.cdt.core/schema/UNCPathConverter.exsd @@ -6,10 +6,9 @@ - [Enter description of this extension point.] + - @@ -46,7 +45,6 @@ - @@ -61,42 +59,4 @@ - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - diff --git a/core/org.eclipse.cdt.core/schema/externalSettingsProvider.exsd b/core/org.eclipse.cdt.core/schema/externalSettingsProvider.exsd index 63e21057247..c0b1a0f9c4b 100644 --- a/core/org.eclipse.cdt.core/schema/externalSettingsProvider.exsd +++ b/core/org.eclipse.cdt.core/schema/externalSettingsProvider.exsd @@ -1,18 +1,22 @@ - + - The external settings provider would be used to specify provider of include/macro/libraryan settings to be used/applied for the build configuration associated with this provider. + The external settings provider is used to specify a provider of include/macro/library settings to be used for the associated build configuration. Any number of setting providers can be associated with the build configurations. -This functionality might be used, e.g. by the External SDKs to allow automatic andjustment of the project settings for the projects using thes SDKs, e.g. adding include paths, symbols, etc. +This functionality might be used, e.g. by the External SDKs to allow automatic andjustment of the project settings for the projects using these SDKs, e.g. adding include paths, symbols, etc. - + + + + + @@ -43,7 +47,6 @@ This functionality might be used, e.g. by the External SDKs to allow automatic a - @@ -58,7 +61,6 @@ This functionality might be used, e.g. by the External SDKs to allow automatic a - @@ -67,41 +69,4 @@ This functionality might be used, e.g. by the External SDKs to allow automatic a 4.0 - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - diff --git a/core/org.eclipse.cdt.core/schema/language.exsd b/core/org.eclipse.cdt.core/schema/language.exsd index 31852fe4c1b..842e380f0af 100644 --- a/core/org.eclipse.cdt.core/schema/language.exsd +++ b/core/org.eclipse.cdt.core/schema/language.exsd @@ -9,7 +9,6 @@ This extension point is used to declare a language or language variant. Languages define how the C model of a file is created (e.g. to populate the outline view). It also provides hooks to override the low level parsing of translation units into an abstract syntax tree. Practically this is limited to C/C++ language variants only. Completely different languages cannot be modelled reasonably using this extension point. - @@ -44,7 +43,6 @@ - @@ -79,7 +77,6 @@ - @@ -91,7 +88,6 @@ - @@ -113,7 +109,6 @@ - @@ -122,7 +117,6 @@ CDT 3.1 - @@ -139,7 +133,6 @@ </pre> - @@ -148,7 +141,6 @@ Clients need to extend the abstract class <code>org.eclipse.core.model.AbstractLanguage</code>. - @@ -163,7 +155,6 @@ </p> - @@ -176,5 +167,4 @@ accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - diff --git a/core/org.eclipse.cdt.core/schema/projectConverter.exsd b/core/org.eclipse.cdt.core/schema/projectConverter.exsd index d034a588c70..1ed4f11b611 100644 --- a/core/org.eclipse.cdt.core/schema/projectConverter.exsd +++ b/core/org.eclipse.cdt.core/schema/projectConverter.exsd @@ -1,16 +1,20 @@ - + - [Enter description of this extension point.] + - + + + + + @@ -41,7 +45,6 @@ - @@ -70,50 +73,4 @@ - - - - - - - [Enter the first release in which this extension point appears.] - - - - - - - - - [Enter extension point usage example here.] - - - - - - - - - [Enter API information here.] - - - - - - - - - [Enter information about supplied implementation of this extension point.] - - - - - - - - - - - - diff --git a/core/org.eclipse.cdt.core/schema/tagger.exsd b/core/org.eclipse.cdt.core/schema/tagger.exsd index 98d37683785..184963c97e5 100644 --- a/core/org.eclipse.cdt.core/schema/tagger.exsd +++ b/core/org.eclipse.cdt.core/schema/tagger.exsd @@ -9,9 +9,7 @@ This extension point allows extensions to contribute to the parsed nodes. When PDOM nodes are tagged, the content of the tag is stored in to the Database. The information for other nodes, e.g., the AST, is stored in memory. - - @@ -48,7 +46,6 @@ - @@ -67,14 +64,12 @@ A unique identifier for this tagger's contributions. - The local id will be appended to the contributing plugin's id (separated with a dot '.') to form the globally unique identifier for this tagger. This id is used to uniquely associate the tag with this plugin. - @@ -83,7 +78,6 @@ The local id will be appended to the contributing plugin's id (separated wi 8.2 - @@ -112,7 +106,6 @@ The local id will be appended to the contributing plugin's id (separated wi </p> - @@ -121,8 +114,6 @@ The local id will be appended to the contributing plugin's id (separated wi The contributed class must implement <code>org.eclipse.cdt.core.dom.ast.tag.IBindingTagger</code> - - @@ -135,5 +126,4 @@ which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - diff --git a/core/org.eclipse.cdt.core/schema/templateAssociations.exsd b/core/org.eclipse.cdt.core/schema/templateAssociations.exsd index 057253b894b..f97574fbb49 100644 --- a/core/org.eclipse.cdt.core/schema/templateAssociations.exsd +++ b/core/org.eclipse.cdt.core/schema/templateAssociations.exsd @@ -1,6 +1,6 @@ - + @@ -9,9 +9,11 @@ This extension-point allows developers to specify toolchains that should be enabled for selection for use with a pre-existing template. This solves the problem over how ISV's can have templates defined and shipped with CDT support their own toolchains, without having to modify CDT itself. - + + + Each extension consists of a sequence of template elements, each of which define child elements for the new toolchains that should be enabled for selection during new project creation. @@ -46,7 +48,6 @@ - @@ -59,11 +60,13 @@ The unique identifier of a toolchain contributed to the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension point. + + + - @@ -79,27 +82,27 @@ The unique identifier of the template-contribution (the id in plugin.xml rather than the template.xml) that should have the specified additional toolchains enabled for selection during new project creation. + + + - - This extension point was added in CDT 4.0 + CDT 4.0 - If you developed toolchain's with ids "com.foobar.toolchain1.base" and "com.foobar.toolchain2.base", which you wanted enabled for the empty project type built into the cdt core, you could use the following to achieve this: - <pre> <extension point="org.eclipse.cdt.core.templateAssociations"> <template id="org.eclipse.cdt.build.core.templates.EmptyProject"> @@ -110,25 +113,6 @@ </pre> - - - - - - - - - - - - - - - - - - - @@ -139,10 +123,8 @@ All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - Contributors: Symbian - Initial API and implementation - diff --git a/core/org.eclipse.cdt.core/schema/templateProcessTypes.exsd b/core/org.eclipse.cdt.core/schema/templateProcessTypes.exsd index 7914b5a3eba..b618e90ffb7 100644 --- a/core/org.eclipse.cdt.core/schema/templateProcessTypes.exsd +++ b/core/org.eclipse.cdt.core/schema/templateProcessTypes.exsd @@ -1,6 +1,6 @@ - + @@ -9,9 +9,11 @@ This extension point is to be extended to define new processes to be used in template descriptors by template writers. - + + + One or more elements of processType should be added as children to this element. @@ -36,7 +38,6 @@ - @@ -71,7 +72,6 @@ - @@ -90,9 +90,7 @@ This is an optional attribute. If specified with a true value, it implies that the template xml need not mention this argument for this param. The attribute does not have any meaning in the context of a child of a complex param or of a child of a complexArray param. - Another thing to note is that arguments corresponding to external=true type params, if not mentioned in the template xml, should be supplied directly through the ValueStore with the key as the param's name. - If not mentioned, this attribute's is treated as false. @@ -101,14 +99,12 @@ If not mentioned, this attribute's is treated as false. This is an optional attribute. If specified with a true value, it implies that the template xml need not mention the value attribute of the argument for this param. The attribute does not have any meaning in the context of a child of a complex param or of a child of a complexArray param. - If not mentioned, this attribute's is treated as false. - @@ -125,7 +121,6 @@ If not mentioned, this attribute's is treated as false. - @@ -150,7 +145,6 @@ If not mentioned, this attribute's is treated as false. - @@ -170,7 +164,6 @@ If not mentioned, this attribute's is treated as false. - @@ -188,16 +181,14 @@ If not mentioned, this attribute's is treated as false. - - This extension point was added in CDT 4.0 + CDT 4.0 - @@ -210,7 +201,6 @@ If not mentioned, this attribute's is treated as false. id="processExample" name="Process Example" point="org.eclipse.cdt.core.templateengine.processTypes"> - <processType name="NewManagedProject" processRunner="org.eclipse.cdt.core.templateengine.process.processes.NewManagedProject"> @@ -224,7 +214,6 @@ If not mentioned, this attribute's is treated as false. nullable="true"/> <simple name="targetType"/> </processType> - <processType name="SetMBSBooleanOptionValue" processRunner="org.eclipse.cdt.core.templateengine.process.processes.SetMBSBooleanOptionValue"> @@ -237,7 +226,6 @@ If not mentioned, this attribute's is treated as false. </baseType> </complexArray> </processType> - <processType name="AddFile" processRunner="org.eclipse.cdt.core.templateengine.process.processes.AddFile"> @@ -248,7 +236,6 @@ If not mentioned, this attribute's is treated as false. <simple name="replaceable"/> </complex> </processType> - <processType name="AppendToMBSStringListOptionValues" processRunner="org.eclipse.cdt.core.templateengine.process.processes.AppendToMBSStringListOptionValues"> @@ -261,24 +248,12 @@ If not mentioned, this attribute's is treated as false. </baseType> </complexArray> </processType> - </extension> </pre> - For more details on how to define your own templates, please check examples provided under <samp>org.eclipse.cdt.gnu.templates</samp> - - - - - - - - - - @@ -287,7 +262,6 @@ For more details on how to define your own templates, please check examples prov An implementation of this extension point is supplied in <samp>org.eclipse.cdt.core.templateengine</samp> - @@ -298,10 +272,8 @@ All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html - Contributors: Bala Torati (Symbian) - Initial API and implementation - diff --git a/core/org.eclipse.cdt.core/schema/templates.exsd b/core/org.eclipse.cdt.core/schema/templates.exsd index 3c0b5750384..91759151075 100644 --- a/core/org.eclipse.cdt.core/schema/templates.exsd +++ b/core/org.eclipse.cdt.core/schema/templates.exsd @@ -1,245 +1,232 @@ - - - - - - - - - This templates extension point facilitates the users to contribute their Template XMLs to the Template Engine plug-in. - - - - - - - - - - Extension point added to Template Engine plugin. Any plugin, which intends to contribute XML templates to the Template Engine must extend this extension point, and add the template element. - - - - - - - - - - - - - - - - - - Id for the extension in the extender plugin. - - - - - - - Optional name attribute. - - - - - - - - - - - - - By adding the templates extension point the users can contribute their Template XMLs to the Template Engine plugin. - - - - - - - - - - - A unique identifier for this template contribution. This does not need to be the same as the id of the template (as defined in template.xml) it is contributing. This allows contributing the same template.xml more than once (for example for multiple project types, or with alternate page sequences). - - - - - - - The path of template.xml (relative to the base of the containing plug-in). For example "templates/TemplateOne/template.xml". This attribute is mandatory. - - - - - - - - - - This attribute is a project type id referring to the cdt project type that the template will be associated with. Project types are contributed to the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension-point. -This attribute is mandatory. CDT pre-defines the following values of the build artifact type property: -<ul> -<li>"org.eclipse.cdt.build.core.buildArtefactType.exe" - to represent executable -<li>"org.eclipse.cdt.build.core.buildArtefactType.staticLib" - to represent static library -<li>"org.eclipse.cdt.build.core.buildArtefactType.sharedLib" - to represent shared library -<li>ISVs can define their own custom build artifact values by contributing to the org.eclipse.cdt.managedbuilder.core.buildProperties extension point. -</ul> -It's no longer manditory since templates are no longer organized by project type. Template catogories replace that functionality. - - - - - - - If true this template contribution should appear as a folder. Defaults to false. - - - - - - - filterPattern is a java.util.regex.Pattern format string which is used to match against build configuration ids. This is an optional attribute, if absent will all configurations will match. - - - - - - - A class that implements org.eclipse.cdt.templateengine.IPagesAfterTemplateSelectionProvider interface to create pages that will be appended to the pages returned from TemplatesChoiceWizard.getPagesAfterTemplateSelection(). - - - - - - - - - - - - - This element is used to reference an existing toolchain by its unique identifier. - - - - - - - The unique identifier of a toolchain contributed to the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension point. - - - - - - - - - - Used to arrange templates in a hierarchy in the UI. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - id of parent category. - - - - - - - - - - - - - - - - - - - - This extension point was added in CDT 4.0 - - - - - - - - - The following is an example of the extension point usage: -<p> -<pre> - <extension point="org.eclipse.cdt.core.templates"> - <template - id="org.foobar.templates.MyExampleTemplate" - location="templates/MyExampleTemplate/template.xml" - projectType="org.eclipse.cdt.build.core.buildArtefactType.exe" - filterPattern=".*"> - </template> - </extension> -</pre> - -For more details on how to define your own templates, please check examples provided under <samp>org.eclipse.cdt.ui.templateengine</samp> - - - - - - - - - An implementation of this extension point is supplied in <samp>org.eclipse.cdt.templateengine</samp> - - - - - - - - - Copyright (c) 2007 Symbian Software Limited and others. -All rights reserved. This program and the accompanying materials -are made available under the terms of the Eclipse Public License v1.0 -which accompanies this distribution, and is available at -http://www.eclipse.org/legal/epl-v10.html - -Contributors: -Symbian - Initial API and implementation - - - - + + + + + + + + + This templates extension point facilitates the users to contribute their Template XMLs to the Template Engine plug-in. + + + + + + + + + Extension point added to Template Engine plugin. Any plugin, which intends to contribute XML templates to the Template Engine must extend this extension point, and add the template element. + + + + + + + + + + + + + + + + + + Id for the extension in the extender plugin. + + + + + + + Optional name attribute. + + + + + + + + + + + + By adding the templates extension point the users can contribute their Template XMLs to the Template Engine plugin. + + + + + + + + + + + A unique identifier for this template contribution. This does not need to be the same as the id of the template (as defined in template.xml) it is contributing. This allows contributing the same template.xml more than once (for example for multiple project types, or with alternate page sequences). + + + + + + + The path of template.xml (relative to the base of the containing plug-in). For example "templates/TemplateOne/template.xml". This attribute is mandatory. + + + + + + + + + + This attribute is a project type id referring to the cdt project type that the template will be associated with. Project types are contributed to the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension-point. +This attribute is mandatory. CDT pre-defines the following values of the build artifact type property: +<ul> +<li>"org.eclipse.cdt.build.core.buildArtefactType.exe" - to represent executable +<li>"org.eclipse.cdt.build.core.buildArtefactType.staticLib" - to represent static library +<li>"org.eclipse.cdt.build.core.buildArtefactType.sharedLib" - to represent shared library +<li>ISVs can define their own custom build artifact values by contributing to the org.eclipse.cdt.managedbuilder.core.buildProperties extension point. +</ul> +It's no longer manditory since templates are no longer organized by project type. Template catogories replace that functionality. + + + + + + + If true this template contribution should appear as a folder. Defaults to false. + + + + + + + filterPattern is a java.util.regex.Pattern format string which is used to match against build configuration ids. This is an optional attribute, if absent will all configurations will match. + + + + + + + A class that implements org.eclipse.cdt.templateengine.IPagesAfterTemplateSelectionProvider interface to create pages that will be appended to the pages returned from TemplatesChoiceWizard.getPagesAfterTemplateSelection(). + + + + + + + + + + + + This element is used to reference an existing toolchain by its unique identifier. + + + + + + + The unique identifier of a toolchain contributed to the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension point. + + + + + + + + + Used to arrange templates in a hierarchy in the UI. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + id of parent category. + + + + + + + + + + + + + + + + + + CDT 4.0 + + + + + + + + The following is an example of the extension point usage: +<p> +<pre> + <extension point="org.eclipse.cdt.core.templates"> + <template + id="org.foobar.templates.MyExampleTemplate" + location="templates/MyExampleTemplate/template.xml" + projectType="org.eclipse.cdt.build.core.buildArtefactType.exe" + filterPattern=".*"> + </template> + </extension> +</pre> +For more details on how to define your own templates, please check examples provided under <samp>org.eclipse.cdt.ui.templateengine</samp> + + + + + + + + An implementation of this extension point is supplied in <samp>org.eclipse.cdt.templateengine</samp> + + + + + + + + Copyright (c) 2007 Symbian Software Limited and others. +All rights reserved. This program and the accompanying materials +are made available under the terms of the Eclipse Public License v1.0 +which accompanies this distribution, and is available at +http://www.eclipse.org/legal/epl-v10.html +Contributors: +Symbian - Initial API and implementation + + +