diff options
Diffstat (limited to 'core/org.eclipse.cdt.core/schema/templateAssociations.exsd')
| -rw-r--r-- | core/org.eclipse.cdt.core/schema/templateAssociations.exsd | 40 |
1 files changed, 11 insertions, 29 deletions
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 @@ <?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'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'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> </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> |