Registering report classes through plug-ins

You can register report classes using a plug-in when you want to distribute the class widely and install it on multiple machines. This lets each user install a plug-in that holds the report class, rather than going through the preferences notebook.

The plug-in's plugin.xml file will typically look something like this:

<requires>
    <import plugin="org.junit" />
    <import plugin="org.eclipse.core.boot" />
    <import plugin="org.eclipse.core.resources" />
    <import plugin="org.eclipse.core.runtime" />
    <import plugin="org.eclipse.jdt.core" />
    <import plugin="org.eclipse.jdt.ui" />
    <import plugin="org.eclipse.ui" />
    <import plugin="org.eclipse.hyades.test.ui" />
    <import plugin="org.eclipse.hyades.test.common" />
    <import plugin="org.eclipse.hyades.models.common" />
    <import plugin="org.eclipse.hyades.execution.remote" />
    <import plugin="org.eclipse.hyades.execution.harness" />
    <import plugin="org.eclipse.hyades.execution.core" />
    <import plugin="org.eclipse.hyades.execution.local" />
</requires>

<extension point="org.eclipse.hyades.ui.reportExtensions">
<reportDescriptions>
<reportDescription name="reportGenerator1" classPath="d:\work\reports\report1.jar" class="MyReportGenerator1"/>
<reportDescription name="reportGenerator2" classPath="d:\work\reports\reports2" class="MyReportGenerator2"/>
</reportDescriptions>
</extension>

Related tasks
Defining new report generators

Related reference
Test suite reports API

(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.