mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-06-07 17:56:01 +02:00
Code Issues Wiki Activity

[bug 417138] Various schema cleanups; English grammar fixes; adding translatable, identifier-type, etc.

Browse source 
Change-Id: I1c10b4171bba0f8d64f41970eae1b2971bc53476
Signed-off-by: Jesse Weinstein <Jesse.Weinstein@clinicomp.com>
Reviewed-on: https://git.eclipse.org/r/16395
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
IP-Clean: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Tested-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
This commit is contained in:
Jesse Weinstein 2013-09-12 17:26:29 -04:00 • committed by Sergey Prigogin
parent 5c358c649c
commit 484c089036
24 changed files with 1323 additions and 1950 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
core/org.eclipse.cdt.core/schema/BinaryParser.exsd
View file

@ -6,10 +6,9 @@
<meta.schema plugin="org.eclipse.cdt.core" id="BinaryParser" name="BinaryParser"/>
</appInfo>
<documentation>
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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -43,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="cextension">
<complexType>
<sequence>
@ -52,7 +50,6 @@
</sequence>
</complexType>
</element>
<element name="run">
<complexType>
<attribute name="class" type="string" use="required">
@ -67,7 +64,6 @@
</attribute>
</complexType>
</element>
<element name="filter">
<annotation>
<appInfo>
@ -106,7 +102,6 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -115,8 +110,6 @@
CDT 2.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
@ -125,8 +118,6 @@
Plug-ins that want to extend this extension point must implement &lt;samp&gt;org.eclipse.cdt.core.IBinaryParser&lt;/samp&gt; interface.
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -139,5 +130,4 @@ which accompanies this distribution, and is available at&lt;br/&gt;
http://www.eclipse.org/legal/epl-v10.html&lt;br/&gt;
</documentation>
</annotation>
</schema>

61
core/org.eclipse.cdt.core/schema/CBuildConsole.exsd
View file

@ -1,16 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="CBuildConsole" name="C/C++ Build Console"/>
</appInfo>
<documentation>
[Enter description of this extension point.]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="CBuildConsole" minOccurs="1" maxOccurs="unbounded"/>
@ -38,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="CBuildConsole">
<complexType>
<attribute name="id" type="string">
@ -51,59 +54,13 @@
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
Class which implents org.eclipse.cdt.core.resources.IConsole
A class which implements org.eclipse.cdt.core.resources.IConsole
</documentation>
<appInfo>
<meta.attribute kind="java"/>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.core.resources.IConsole"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

71
core/org.eclipse.cdt.core/schema/CConfigurationDataProvider.exsd
View file

@ -1,16 +1,21 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="CConfigurationDataProvider" name="CConfigurationData provider"/>
</appInfo>
<documentation>
[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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="provider"/>
@ -41,84 +46,32 @@
</attribute>
</complexType>
</element>
<element name="provider">
<complexType>
<attribute name="natures" type="string">
<annotation>
<documentation>
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.
</documentation>
</annotation>
</attribute>
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
class implementing the org.eclipse.cdt.core.settings.model.extension.CConfigurationDataProvider
A class which extends org.eclipse.cdt.core.settings.model.extension.CConfigurationDataProvider
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.core.settings.model.extension.CConfigurationDataProvider"/>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.core.settings.model.extension.CConfigurationDataProvider:"/>
</appInfo>
</annotation>
</attribute>
<attribute name="conflictingNatures" type="string">
<annotation>
<documentation>
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.
</documentation>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

9
core/org.eclipse.cdt.core/schema/CExtensionGeneric.exsd
View file

@ -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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -43,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="cextension">
<complexType>
<sequence>
@ -51,7 +49,6 @@
</sequence>
</complexType>
</element>
<element name="run">
<complexType>
<attribute name="class" type="string" use="required">
@ -66,11 +63,6 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -83,5 +75,4 @@ which accompanies this distribution, and is available at&lt;br/&gt;
http://www.eclipse.org/legal/epl-v10.html&lt;br/&gt;
</documentation>
</annotation>
</schema>

47
core/org.eclipse.cdt.core/schema/CIndex.exsd
View file

@ -9,7 +9,6 @@
This extension point groups extensions to the index functionality in CDT
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -48,7 +47,6 @@
</attribute>
</complexType>
</element>
<element name="ExportProjectProvider">
<annotation>
<documentation>
@ -57,9 +55,7 @@
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).
&lt;p&gt;
&lt;b&gt;Invoking the application as a headless application&lt;/b&gt;
This example ant file shows how to invoke the tool headlessly, the same approach would work from a shell or batch file.
&lt;pre&gt;
&lt;project name=&quot;Generate PDOM&quot; default=&quot;generate&quot;&gt;
&lt;target name=&quot;generate&quot;&gt;
@ -102,16 +98,15 @@ In the Argument tabs provide (for example)
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
the fully qualified name of the IExportProjectProvider implementation to register
The fully qualified name of the IExportProjectProvider implementation to register.
</documentation>
<appInfo>
<meta.attribute kind="java"/>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.core.index.export.IExportProjectProvider"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<element name="ReadOnlyPDOMProvider">
<annotation>
<documentation>
@ -125,23 +120,18 @@ This subelement of CIndex allows ISVs to contribute read-only prebuilt PDOM file
&lt;ReadOnlyPDOMProvider class=&quot;com.acme.ide.index.AcmeSDKProvider&quot;/&gt;
&lt;/CIndex&gt;
&lt;/pre&gt;
and the corresponding implementation
&lt;pre&gt;
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() {
@ -165,7 +155,7 @@ public class AcmeSDKProvider implements IReadOnlyPDOMProvider {
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
The fully qualified name of the IReadOnlyPDOMProvider implementation to register
The fully qualified name of the IReadOnlyPDOMProvider implementation to register.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.core.index.provider.IReadOnlyPDOMProvider"/>
@ -174,7 +164,6 @@ public class AcmeSDKProvider implements IReadOnlyPDOMProvider {
</attribute>
</complexType>
</element>
<element name="ReadOnlyIndexFragmentProvider">
<annotation>
<documentation>
@ -192,7 +181,7 @@ The only information needed for this extension point is the fully qualified name
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
The fully qualified name of a class implementing IIndexFragmentProvider interface.
The fully qualified name of a class implementing IIndexFragmentProvider.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.internal.core.index.provider.IIndexFragmentProvider"/>
@ -201,7 +190,6 @@ The only information needed for this extension point is the fully qualified name
</attribute>
</complexType>
</element>
<element name="FragmentProviderUsage">
<annotation>
<documentation>
@ -258,7 +246,7 @@ The only information needed for this extension point is the fully qualified name
</documentation>
</annotation>
</attribute>
<attribute name="editor" type="boolean" use="optional">
<attribute name="editor" type="boolean">
<annotation>
<documentation>
Whether the fragment provider shall be used for C/C++ editor.
@ -267,18 +255,6 @@ The only information needed for this extension point is the fully qualified name
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
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
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -287,7 +263,6 @@ For export functionality, see package org.eclipse.cdt.core.index.export
4.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
@ -296,7 +271,6 @@ For export functionality, see package org.eclipse.cdt.core.index.export
See subelement documentation
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
@ -305,7 +279,6 @@ For export functionality, see package org.eclipse.cdt.core.index.export
See subelement documentation
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -318,5 +291,13 @@ which accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
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
</documentation>
</annotation>
</schema>

43
core/org.eclipse.cdt.core/schema/CIndexer.exsd
View file

@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="CDTIndexer" name="CDT Indexer"/>
@ -9,8 +9,12 @@
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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="run"/>
@ -38,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="run">
<complexType>
<attribute name="class" type="string" use="required">
@ -53,25 +56,6 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
CDT 3.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
@ -80,23 +64,12 @@
Plug-ins that want to extend this extension point must implement &lt;samp&gt;org.eclipse.cdt.core.index.IIndexer&lt;/samp&gt; interface.
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
CDT 3.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

52
core/org.eclipse.cdt.core/schema/CProject.exsd
View file

@ -1,16 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="CProject" name="C/C++ Project Description"/>
</appInfo>
<documentation>
[Enter description of this extension point]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="cproject"/>
@ -38,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="cproject">
<complexType>
<attribute name="class" type="string" use="required">
@ -47,14 +50,14 @@
Class which implements org.eclipse.cdt.core.ICOwner
</documentation>
<appInfo>
<meta.attribute kind="java"/>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.core.ICOwner"/>
</appInfo>
</annotation>
</attribute>
<attribute name="natureID" type="string">
<annotation>
<documentation>
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.
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.
</documentation>
</annotation>
</attribute>
@ -67,41 +70,4 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

47
core/org.eclipse.cdt.core/schema/CProjectDescriptionStorage.exsd
View file

@ -2,19 +2,18 @@
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appinfo>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="CProjectDescriptionStorage" name="%CProjectDescription.name"/>
</appinfo>
</appInfo>
<documentation>
This extension point allows contributors to provide their own implementation of the CProjectDescriptionStorage backing store.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appinfo>
<appInfo>
<meta.element internal="true" />
</appinfo>
</appInfo>
</annotation>
<complexType>
<sequence minOccurs="1" maxOccurs="unbounded">
@ -39,14 +38,13 @@
<documentation>
</documentation>
<appinfo>
<appInfo>
<meta.attribute translatable="true"/>
</appinfo>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<element name="CProjectStorageType">
<annotation>
<documentation>
@ -59,9 +57,9 @@
<documentation>
A factory class that implements ICProjectDescriptionStorageType to create AbstractCProjectDescriptionStorages for given IProjects
</documentation>
<appinfo>
<appInfo>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.internal.core.settings.model.ICProjectDescriptionStorageType"/>
</appinfo>
</appInfo>
</annotation>
</attribute>
<attribute name="id" type="string" use="required">
@ -69,6 +67,9 @@
<documentation>
Id of this particular project description storage type
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
<attribute name="version" type="string" use="required">
@ -100,41 +101,27 @@ This String value must be compatible with org.eclipse.osgi.framework.version
<documentation>
Human readable name of this project description type
</documentation>
<appinfo>
<appInfo>
<meta.attribute translatable="true"/>
</appinfo>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appinfo>
<appInfo>
<meta.section type="since"/>
</appinfo>
</appInfo>
<documentation>
6.0
</documentation>
</annotation>
<annotation>
<appinfo>
<meta.section type="apiinfo"/>
</appinfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appinfo>
<appInfo>
<meta.section type="implementation"/>
</appinfo>
</appInfo>
<documentation>
See the example XmlProjectDescriptionStorage &amp; XmlProjectDescriptionStorage2 in this plugin
</documentation>
</annotation>
</schema>

65
core/org.eclipse.cdt.core/schema/CodeFormatter.exsd
View file

@ -1,16 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="CodeFormatter" name="Code Formatter"/>
</appInfo>
<documentation>
[Enter description of this extension point.]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="codeFormatter" minOccurs="1" maxOccurs="unbounded"/>
@ -38,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="codeFormatter">
<complexType>
<attribute name="id" type="string" use="required">
@ -46,6 +49,9 @@
<documentation>
A unique name that will be used to reference this code formatter
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
<attribute name="name" type="string" use="required">
@ -53,12 +59,15 @@
<documentation>
A translatable name that will be used for presenting this formatter in the UI.
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
</appInfo>
</annotation>
</attribute>
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
a fully qualified name of the Java class that implements &lt;samp&gt;org.eclipse.cdt.core.formatter.CodeFormatter&lt;/samp&gt; abstract class.
A fully qualified name of the Java class that extends the &lt;samp&gt;org.eclipse.cdt.core.formatter.CodeFormatter&lt;/samp&gt; abstract class.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.core.formatter.CodeFormatter"/>
@ -67,50 +76,4 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

68
core/org.eclipse.cdt.core/schema/EFSExtensionProvider.exsd
View file

@ -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.
</documentation>
</annotation>
<element name="EFSExtensionProvider">
<annotation>
<documentation>
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.
</documentation>
</annotation>
<complexType>
<attribute name="scheme" type="string" use="required">
<annotation>
<documentation>
The URI scheme of an EFS filesystem this utility provides support for.
</documentation>
</annotation>
</attribute>
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
Java class which extends from org.eclipse.cdt.core.EFSFileSystemSupplementarySupportProvider to provide support for the filesystem.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.core.EFSExtensionProvider:"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<element name="extension">
<annotation>
<appInfo>
@ -73,7 +45,32 @@
</attribute>
</complexType>
</element>
<element name="EFSExtensionProvider">
<annotation>
<documentation>
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.
</documentation>
</annotation>
<complexType>
<attribute name="scheme" type="string" use="required">
<annotation>
<documentation>
The URI scheme of an EFS filesystem this utility provides support for.
</documentation>
</annotation>
</attribute>
<attribute name="class" type="string" use="required">
<annotation>
<documentation>
Java class which extends from org.eclipse.cdt.core.EFSFileSystemSupplementarySupportProvider to provide support for the filesystem.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.cdt.core.EFSExtensionProvider:"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -82,17 +79,6 @@
5.2
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
@ -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.
</documentation>
</annotation>
</schema>

33
core/org.eclipse.cdt.core/schema/ErrorParser.exsd
View file

@ -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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -43,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="errorparser">
<complexType>
<sequence>
@ -55,6 +53,9 @@
<documentation>
ID of the error parser. If attribute is missing error parser ID is constructed appending Simple ID of extension to plugin ID.
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
<attribute name="name" type="string">
@ -62,12 +63,15 @@
<documentation>
Name of the error parser. If this attribute is missing extension name is taken.
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
</appInfo>
</annotation>
</attribute>
<attribute name="class" type="string" use="default" value="org.eclipse.cdt.core.errorparsers.RegexErrorParser">
<annotation>
<documentation>
a fully qualified name of the Java class that implements &lt;samp&gt;org.eclipse.cdt.core.IErrorParser&lt;/samp&gt; interface.
a fully qualified name of the Java class that implements &lt;samp&gt;org.eclipse.cdt.core.IErrorParser&lt;/samp&gt;
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn=":org.eclipse.cdt.core.errorparsers.IErrorParser"/>
@ -76,7 +80,6 @@
</attribute>
</complexType>
</element>
<element name="pattern">
<annotation>
<documentation>
@ -87,7 +90,7 @@
<attribute name="severity" use="required">
<annotation>
<documentation>
Attribute &quot;severity&quot; specifies which severity should be used to display the marker in Problems View. There are 3 levels of severity, &quot;Error&quot;, &quot;Warning&quot; and &quot;Info&quot;. &quot;Ignore&quot; 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, &quot;Error&quot;, &quot;Warning&quot; and &quot;Info&quot;. The forth option, &quot;Ignore&quot; tells the system to stop checking the line against the other patterns without causing it to show up in the Problems View.
</documentation>
</annotation>
<simpleType>
@ -106,7 +109,7 @@
<attribute name="regex" type="string" use="default" value="(.*)">
<annotation>
<documentation>
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.
</documentation>
</annotation>
</attribute>
@ -141,20 +144,17 @@
<attribute name="eat-processed-line" type="boolean" use="required">
<annotation>
<documentation>
The attribute defines if a line matched by the pattern is prevented or allowed to be processed by the rest of patterns. &quot;No&quot; 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. &quot;false&quot; allows several patterns to evaluate the same line.
</documentation>
</annotation>
</attribute>
</complexType>
</element>
<element name="context">
<annotation>
<documentation>
Use this element to specify the context where an error parser can be used. If none is specified, a default context type will be &quot;build&quot;.
An example of context type is &quot;build&quot;. Only error parsers in this context are used to parse build output. You can see these error parsers in the &quot;C/C++&quot; &gt; &quot;Build&quot; &gt; &quot;Settings&quot; 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 &quot;build&quot;.
An example of a context type is &quot;build&quot;. Only error parsers in this context are used to parse build output. You can see these error parsers in the &quot;C/C++&quot; &gt; &quot;Build&quot; &gt; &quot;Settings&quot; 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.
</documentation>
</annotation>
@ -168,7 +168,6 @@ An error parser can be assigned to more than one context type. Clients contribut
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -177,14 +176,12 @@ An error parser can be assigned to more than one context type. Clients contribut
CDT 1.2
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
&lt;br/&gt;
package org.eclipse.cdt.example.errorparser;&lt;br/&gt;
package org.eclipse.cdt.example.errorparser;&lt;br/&gt;
&lt;br/&gt;
import org.eclipse.cdt.core.IMarkerGenerator;&lt;br/&gt;
import org.eclipse.cdt.core.errorparsers.AbstractErrorParser;&lt;br/&gt;
@ -209,7 +206,6 @@ public class SampleErrorParser extends AbstractErrorParser {&lt;br/&gt;
}&lt;br/&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
@ -223,7 +219,6 @@ Another good choice is to extend &lt;samp&gt;org.eclipse.cdt.core.errorparsers.A
ErrorParsers dealing with multi-line messages should implement &lt;samp&gt;org.eclipse.cdt.core.IErrorParser2&lt;/samp&gt; interface.
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
@ -232,7 +227,6 @@ ErrorParsers dealing with multi-line messages should implement &lt;samp&gt;org.e
For another example of implementation see org.eclipse.cdt.internal.errorparsers.GCCErrorParser
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -245,5 +239,4 @@ which accompanies this distribution, and is available at&lt;br/&gt;
http://www.eclipse.org/legal/epl-v10.html&lt;br/&gt;
</documentation>
</annotation>
</schema>

34
core/org.eclipse.cdt.core/schema/LanguageSettingsProvider.exsd
View file

@ -9,7 +9,6 @@
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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -49,7 +48,6 @@
</attribute>
</complexType>
</element>
<element name="provider">
<annotation>
<documentation>
@ -79,6 +77,9 @@ Default constructor (constructor without arguments) of this class must be public
<documentation>
Unique ID of the provider.
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
<attribute name="name" type="string" use="required">
@ -86,6 +87,9 @@ Default constructor (constructor without arguments) of this class must be public
<documentation>
Name of the provider. This name will be presented to a user in UI.
</documentation>
<appInfo>
<meta.attribute translatable="true"/>
</appInfo>
</annotation>
</attribute>
<attribute name="parameter" type="string">
@ -105,7 +109,6 @@ The value &quot;true&quot; of this attribute is meaningful only for providers ca
</attribute>
</complexType>
</element>
<element name="language-scope">
<annotation>
<documentation>
@ -124,7 +127,6 @@ The value &quot;true&quot; of this attribute is meaningful only for providers ca
</attribute>
</complexType>
</element>
<element name="entry">
<annotation>
<documentation>
@ -139,7 +141,6 @@ The value &quot;true&quot; of this attribute is meaningful only for providers ca
<annotation>
<documentation>
Kind of language settings entry which maps to compiler options. For example, following mapping is used for gcc options:
&lt;br&gt;&quot;&lt;samp&gt;-I&lt;/samp&gt;&quot; : includePath
&lt;br&gt;&quot;&lt;samp&gt;-D&lt;/samp&gt;&quot; : macro
&lt;br&gt;&quot;&lt;samp&gt;-include&lt;/samp&gt;&quot; : includeFile
@ -185,7 +186,6 @@ The value &quot;true&quot; of this attribute is meaningful only for providers ca
</attribute>
</complexType>
</element>
<element name="flag">
<annotation>
<documentation>
@ -224,7 +224,6 @@ The value &quot;true&quot; of this attribute is meaningful only for providers ca
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -233,16 +232,6 @@ The value &quot;true&quot; of this attribute is meaningful only for providers ca
CDT 8.1
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
@ -254,16 +243,6 @@ For those cases where contributed settings entries (representing the compiler op
&lt;br/&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -276,5 +255,4 @@ which accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
</documentation>
</annotation>
</schema>

57
core/org.eclipse.cdt.core/schema/PathEntryContainerInitializer.exsd
View file

@ -1,16 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="pathEntryContainerInitializer" name="Path Entry Container Initializers"/>
</appInfo>
<documentation>
[Enter description of this extension point.]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="pathEntryContainerInitializer"/>
@ -38,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="pathEntryContainerInitializer">
<complexType>
<attribute name="id" type="string" use="required">
@ -60,50 +63,4 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

48
core/org.eclipse.cdt.core/schema/ProcessList.exsd
View file

@ -1,16 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="ProcessList" name="Process List Query Exentsion"/>
</appInfo>
<documentation>
[Enter description of this extension point]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="processList"/>
@ -38,7 +42,6 @@
</attribute>
</complexType>
</element>
<element name="processList">
<complexType>
<attribute name="class" type="string" use="required">
@ -60,41 +63,4 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

32
core/org.eclipse.cdt.core/schema/RefreshExclusionFactory.exsd
View file

@ -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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -46,7 +45,6 @@
</attribute>
</complexType>
</element>
<element name="exclusionFactory">
<complexType>
<attribute name="factoryClass" type="string" use="required">
@ -81,7 +79,6 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -90,34 +87,6 @@
5.3.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -130,5 +99,4 @@ this distribution, and is available at &lt;a
href=&quot;http://www.eclipse.org/legal/epl-v10.html&quot;&gt;http://www.eclipse.org/legal/epl-v10.html&lt;/a&gt;
</documentation>
</annotation>
</schema>

45
core/org.eclipse.cdt.core/schema/ScannerInfoProvider2.exsd
View file

@ -6,10 +6,9 @@
<meta.schema plugin="org.eclipse.cdt.core" id="ScannerInfoProvider2" name="Scanner Info Provider"/>
</appInfo>
<documentation>
[Enter description of this extension point.]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -46,7 +45,6 @@
</attribute>
</complexType>
</element>
<element name="provider">
<complexType>
<attribute name="class" type="string" use="required">
@ -64,46 +62,11 @@
<documentation>
The id of the build command this scanner info provider provides for.
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
</schema>

42
core/org.eclipse.cdt.core/schema/UNCPathConverter.exsd
View file

@ -6,10 +6,9 @@
<meta.schema plugin="org.eclipse.cdt.core" id="UNCPathConverter" name="%UNCPathConverter.name"/>
</appInfo>
<documentation>
[Enter description of this extension point.]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -46,7 +45,6 @@
</attribute>
</complexType>
</element>
<element name="UNCPathConverter">
<complexType>
<attribute name="class" type="string" use="required">
@ -61,42 +59,4 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiinfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
</schema>

51
core/org.eclipse.cdt.core/schema/externalSettingsProvider.exsd
View file

@ -1,18 +1,22 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="externalSettingsProvider" name="External Settings provider"/>
</appInfo>
<documentation>
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.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="provider"/>
@ -43,7 +47,6 @@ This functionality might be used, e.g. by the External SDKs to allow automatic a
</attribute>
</complexType>
</element>
<element name="provider">
<complexType>
<attribute name="class" type="string" use="required">
@ -58,7 +61,6 @@ This functionality might be used, e.g. by the External SDKs to allow automatic a
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -67,41 +69,4 @@ This functionality might be used, e.g. by the External SDKs to allow automatic a
4.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

10
core/org.eclipse.cdt.core/schema/language.exsd
View file

@ -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.
</documentation>
</annotation>
<element name="extension">
<complexType>
<sequence minOccurs="1" maxOccurs="unbounded">
@ -44,7 +43,6 @@
</attribute>
</complexType>
</element>
<element name="language">
<complexType>
<sequence minOccurs="0" maxOccurs="unbounded">
@ -79,7 +77,6 @@
</attribute>
</complexType>
</element>
<element name="contentType">
<complexType>
<attribute name="id" type="string">
@ -91,7 +88,6 @@
</attribute>
</complexType>
</element>
<element name="pdomLinkageFactory">
<complexType>
<attribute name="id" type="string" use="required">
@ -113,7 +109,6 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -122,7 +117,6 @@
CDT 3.1
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
@ -139,7 +133,6 @@
&lt;/pre&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
@ -148,7 +141,6 @@
Clients need to extend the abstract class &lt;code&gt;org.eclipse.core.model.AbstractLanguage&lt;/code&gt;.
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
@ -163,7 +155,6 @@
&lt;/p&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -176,5 +167,4 @@ accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
</documentation>
</annotation>
</schema>

57
core/org.eclipse.cdt.core/schema/projectConverter.exsd
View file

@ -1,16 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="projectConverter" name="project converter"/>
</appInfo>
<documentation>
[Enter description of this extension point.]
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
</annotation>
<complexType>
<sequence>
<element ref="converter"/>
@ -41,7 +45,6 @@
</attribute>
</complexType>
</element>
<element name="converter">
<complexType>
<attribute name="owners" type="string">
@ -70,50 +73,4 @@
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
[Enter the first release in which this extension point appears.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
[Enter extension point usage example here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
[Enter API information here.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
[Enter information about supplied implementation of this extension point.]
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
</appInfo>
<documentation>
</documentation>
</annotation>
</schema>

10
core/org.eclipse.cdt.core/schema/tagger.exsd
View file

@ -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.
</documentation>
</annotation>
<include schemaLocation="schema://org.eclipse.core.expressions/schema/expressionLanguage.exsd"/>
<element name="extension">
<annotation>
<appInfo>
@ -48,7 +46,6 @@
</attribute>
</complexType>
</element>
<element name="bindingTagger">
<complexType>
<sequence>
@ -67,14 +64,12 @@
<annotation>
<documentation>
A unique identifier for this tagger&apos;s contributions.
The local id will be appended to the contributing plugin&apos;s id (separated with a dot &apos;.&apos;) to form the globally unique identifier for this tagger. This id is used to uniquely associate the tag with this plugin.
</documentation>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
@ -83,7 +78,6 @@ The local id will be appended to the contributing plugin&apos;s id (separated wi
8.2
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
@ -112,7 +106,6 @@ The local id will be appended to the contributing plugin&apos;s id (separated wi
&lt;/p&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
@ -121,8 +114,6 @@ The local id will be appended to the contributing plugin&apos;s id (separated wi
The contributed class must implement &lt;code&gt;org.eclipse.cdt.core.dom.ast.tag.IBindingTagger&lt;/code&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -135,5 +126,4 @@ which accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
</documentation>
</annotation>
</schema>

40
core/org.eclipse.cdt.core/schema/templateAssociations.exsd
View file

@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="templateAssociations" name="Template Associations"/>
@ -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&apos;s can have templates defined and shipped with CDT support their own toolchains, without having to modify CDT itself.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
<documentation>
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.
</documentation>
@ -46,7 +48,6 @@
</attribute>
</complexType>
</element>
<element name="toolChain">
<annotation>
<documentation>
@ -59,11 +60,13 @@
<documentation>
The unique identifier of a toolchain contributed to the org.eclipse.cdt.managedbuilder.core.buildDefinitions extension point.
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<element name="template">
<annotation>
<documentation>
@ -79,27 +82,27 @@
<documentation>
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.
</documentation>
<appInfo>
<meta.attribute kind="identifier"/>
</appInfo>
</annotation>
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
This extension point was added in CDT 4.0
CDT 4.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
</appInfo>
<documentation>
If you developed toolchain&apos;s with ids &quot;com.foobar.toolchain1.base&quot; and &quot;com.foobar.toolchain2.base&quot;, which you wanted enabled for the empty project type built into the cdt core, you could use the following to achieve this:
&lt;pre&gt;
&lt;extension point=&quot;org.eclipse.cdt.core.templateAssociations&quot;&gt;
&lt;template id=&quot;org.eclipse.cdt.build.core.templates.EmptyProject&quot;&gt;
@ -110,25 +113,6 @@
&lt;/pre&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
</appInfo>
<documentation>
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -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
</documentation>
</annotation>
</schema>

38
core/org.eclipse.cdt.core/schema/templateProcessTypes.exsd
View file

@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- Schema file written by PDE -->
<schema targetNamespace="org.eclipse.cdt.core">
<schema targetNamespace="org.eclipse.cdt.core" xmlns="http://www.w3.org/2001/XMLSchema">
<annotation>
<appInfo>
<meta.schema plugin="org.eclipse.cdt.core" id="templateProcessTypes" name="Processes Extension point"/>
@ -9,9 +9,11 @@
This extension point is to be extended to define new processes to be used in template descriptors by template writers.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
<meta.element />
</appInfo>
<documentation>
One or more elements of processType should be added as children to this element.
</documentation>
@ -36,7 +38,6 @@
</attribute>
</complexType>
</element>
<element name="processType">
<annotation>
<documentation>
@ -71,7 +72,6 @@
</attribute>
</complexType>
</element>
<element name="simple">
<annotation>
<documentation>
@ -90,9 +90,7 @@
<annotation>
<documentation>
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&apos;s name.
If not mentioned, this attribute&apos;s is treated as false.
</documentation>
</annotation>
@ -101,14 +99,12 @@ If not mentioned, this attribute&apos;s is treated as false.
<annotation>
<documentation>
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&apos;s is treated as false.
</documentation>
</annotation>
</attribute>
</complexType>
</element>
<element name="simpleArray">
<annotation>
<documentation>
@ -125,7 +121,6 @@ If not mentioned, this attribute&apos;s is treated as false.
</attribute>
</complexType>
</element>
<element name="complex">
<annotation>
<documentation>
@ -150,7 +145,6 @@ If not mentioned, this attribute&apos;s is treated as false.
</attribute>
</complexType>
</element>
<element name="complexArray">
<annotation>
<documentation>
@ -170,7 +164,6 @@ If not mentioned, this attribute&apos;s is treated as false.
</attribute>
</complexType>
</element>
<element name="baseType">
<annotation>
<documentation>
@ -188,16 +181,14 @@ If not mentioned, this attribute&apos;s is treated as false.
</sequence>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
This extension point was added in CDT 4.0
CDT 4.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
@ -210,7 +201,6 @@ If not mentioned, this attribute&apos;s is treated as false.
id=&quot;processExample&quot;
name=&quot;Process Example&quot;
point=&quot;org.eclipse.cdt.core.templateengine.processTypes&quot;&gt;
&lt;processType
name=&quot;NewManagedProject&quot;
processRunner=&quot;org.eclipse.cdt.core.templateengine.process.processes.NewManagedProject&quot;&gt;
@ -224,7 +214,6 @@ If not mentioned, this attribute&apos;s is treated as false.
nullable=&quot;true&quot;/&gt;
&lt;simple name=&quot;targetType&quot;/&gt;
&lt;/processType&gt;
&lt;processType
name=&quot;SetMBSBooleanOptionValue&quot;
processRunner=&quot;org.eclipse.cdt.core.templateengine.process.processes.SetMBSBooleanOptionValue&quot;&gt;
@ -237,7 +226,6 @@ If not mentioned, this attribute&apos;s is treated as false.
&lt;/baseType&gt;
&lt;/complexArray&gt;
&lt;/processType&gt;
&lt;processType
name=&quot;AddFile&quot;
processRunner=&quot;org.eclipse.cdt.core.templateengine.process.processes.AddFile&quot;&gt;
@ -248,7 +236,6 @@ If not mentioned, this attribute&apos;s is treated as false.
&lt;simple name=&quot;replaceable&quot;/&gt;
&lt;/complex&gt;
&lt;/processType&gt;
&lt;processType
name=&quot;AppendToMBSStringListOptionValues&quot;
processRunner=&quot;org.eclipse.cdt.core.templateengine.process.processes.AppendToMBSStringListOptionValues&quot;&gt;
@ -261,24 +248,12 @@ If not mentioned, this attribute&apos;s is treated as false.
&lt;/baseType&gt;
&lt;/complexArray&gt;
&lt;/processType&gt;
&lt;/extension&gt;
&lt;/pre&gt;
For more details on how to define your own templates, please check examples provided under
&lt;samp&gt;org.eclipse.cdt.gnu.templates&lt;/samp&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="apiInfo"/>
</appInfo>
<documentation>
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
@ -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 &lt;samp&gt;org.eclipse.cdt.core.templateengine&lt;/samp&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -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
</documentation>
</annotation>
</schema>

15
core/org.eclipse.cdt.core/schema/templates.exsd
View file

@ -9,7 +9,6 @@
This templates extension point facilitates the users to contribute their Template XMLs to the Template Engine plug-in.
</documentation>
</annotation>
<element name="extension">
<annotation>
<appInfo>
@ -50,7 +49,6 @@
</attribute>
</complexType>
</element>
<element name="template">
<annotation>
<documentation>
@ -120,7 +118,6 @@ It&apos;s no longer manditory since templates are no longer organized by project
</attribute>
</complexType>
</element>
<element name="toolChain">
<annotation>
<documentation>
@ -137,7 +134,6 @@ It&apos;s no longer manditory since templates are no longer organized by project
</attribute>
</complexType>
</element>
<element name="category">
<annotation>
<documentation>
@ -167,7 +163,6 @@ It&apos;s no longer manditory since templates are no longer organized by project
</attribute>
</complexType>
</element>
<element name="parentCategory">
<annotation>
<documentation>
@ -184,17 +179,14 @@ It&apos;s no longer manditory since templates are no longer organized by project
</attribute>
</complexType>
</element>
<annotation>
<appInfo>
<meta.section type="since"/>
</appInfo>
<documentation>
This extension point was added in CDT 4.0
CDT 4.0
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="examples"/>
@ -212,11 +204,9 @@ It&apos;s no longer manditory since templates are no longer organized by project
&lt;/template&gt;
&lt;/extension&gt;
&lt;/pre&gt;
For more details on how to define your own templates, please check examples provided under &lt;samp&gt;org.eclipse.cdt.ui.templateengine&lt;/samp&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="implementation"/>
@ -225,7 +215,6 @@ For more details on how to define your own templates, please check examples prov
An implementation of this extension point is supplied in &lt;samp&gt;org.eclipse.cdt.templateengine&lt;/samp&gt;
</documentation>
</annotation>
<annotation>
<appInfo>
<meta.section type="copyright"/>
@ -236,10 +225,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
</documentation>
</annotation>
</schema>