The <code>org.eclipse.mylyn.tasks.bugs.support</code> extension points allows client to provide information for integrated bug reporting. Extensions can specify properties such as URLS and components for creating entries in bug repositories and provide mappings from bundles to bug repositories. These mappings are used by the corresponding UI to support creating bug reports from error log entries for instance.

<p>Clients need to specify a <code>provider</code> extension to describe the entity that provides support and one or more <code>product</code> extensions to describe supported products. Supported products are typically represented by installed features. For each product one or more <code>mapping</code> extension can be specified to associate bundles based on their namespace with the product.
A fully qualified identifier of the target extension point.
An optional identifier of the extension instance.
An optional name of the extension instance.
This element specifies a mapping from a bundle namespace to a product. For example, the namespace prefix <code>org.eclipse</code> will match all org.eclipse.* bundles such as <code>org.eclipse.platform</code> or <code>org.eclipse.mylyn.tasks.ui</code>.

<p>More specific namespaces include or override properties specified in less specific ones for the same product. For example a mapping for the <code>org.eclipse.tasks.ui</code> namespace includes all properties specified for the <code>org.eclipse</code> namespace.

<p>Mappings are only enabled if the nested properties are sufficient to create a bug report, e.g. a repository needs to be specified. To force enablement of a mapping the special value property with the name <code>org.eclipse.mylyn.tasks.bugs.mappingComplete</code> and value <code>true</code> can be specified.
The namespace prefix, e.g. <code>org.eclipse</code>.
The id of the product for this mapping.
This element specifies the properties for a bug repository. The repository must exist in the workspace, e.g. through defining a repository template extension.
The repository URL.
The connector kind of the repository.
A supported product.
The uniquie identifier for this product.
The id of the support provider for this product.
The name of the product. If omitted and <code>featureId</code> or <code>pluginId</code> is specified the name is obtained from the referenced bundle.
A description for the product. If omitted and <code>featureId</code> or <code>pluginId</code> is specified the description is obtained from the referenced bundle.
A 32x32 branding icon. If omitted and <code>featureId</code> or <code>pluginId</code> is specified the icon is obtained from the referenced bundle.
A URL for the product.
The id of a feature that specifies branding information for the product. If specified the product extension is only enabled if the corresponding feature is installed.
The id of a bundle that specifies branding information for the product. If specified the product extension is only enabled if the corresponding plug-in is installed.
This element specifies the value of an attribute for creating bug reports.
The name of the attribute. Supportednames are: <pre>component, description, priority, product, severity, summary, version</pre>
The value of the attribute.
Categories group support providers.
The uniquie identifier for this category.
The name of this category.
An optional description for this category.
An optional integer value to to rank the category. Categories with lower weights are shown first.
This elements describes an entity that provides support.
The uniquie identifier for this provider.
The category of this provider.
The name of this category.
An optional description for this provider.
A 32x32 branding icon.
An optional URL for this provider.
This element specifies a class that handles instances of <code>ISupportRequest</code>s. The framework provides a default handler that creates bug reports based on mappings but clients may customize behavior by providing their own handler.
The unique id of this handler.
The implementation class for this handler.
3.4
<pre> <extension point="org.eclipse.mylyn.tasks.bugs.support"> <!-- category for grouping providers --> <category description="Community supported open source projects" id="org.eclipse.mylyn.tasks.bugs.openSource" name="Open Source Community" weight="900" /> <!-- provider that specifies branding --> <provider categoryId="org.eclipse.mylyn.tasks.bugs.openSource" description="Eclipse open source community bug tracker" icon="icons/branding32/eclipse.png" id="org.eclipse" name="Eclipse.org" url="http://eclipse.org/" /> <!-- mapping for all org.eclipse.* bundles --> <mapping namespace="org.eclipse"> <repository kind="bugzilla" url="https://bugs.eclipse.org/bugs"/> </mapping> <!-- supported product --> <product id="org.eclipse.mylyn" featureId="org.eclipse.mylyn_feature" pluginId="org.eclipse.mylyn" providerId="org.eclipse" url="http://eclipse.org/mylyn/support/" /> <!-- specific mapping for org.eclipse.mylyn.* bundles --> <mapping namespace="org.eclipse.mylyn" productId="org.eclipse.mylyn"> <property name="product" value="Mylyn"/> </mapping> <!-- more specific mapping for org.eclipse.mylyn.tasks.* bundles --> <mapping namespace="org.eclipse.mylyn.tasks" productId="org.eclipse.mylyn"> <property name="component" value="Tasks"/> </mapping> </extension> </pre>
Copyright (c) 2009 Tasktop Technologies 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