Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDE/API Tools/Tasks"

< PDE‎ | API Tools
(API Deprecation)
Line 1: Line 1:
 
API Tools provides a number of tasks to integrate the tooling into your releng builds.  They are available in the org.eclipse.pde.api.tools bundle.  The jarred task code <code>apitooling-ant.jar</code> must be on the Ant classpath.
 
API Tools provides a number of tasks to integrate the tooling into your releng builds.  They are available in the org.eclipse.pde.api.tools bundle.  The jarred task code <code>apitooling-ant.jar</code> must be on the Ant classpath.
 +
 +
If you are running the tasks from an Eclipse target workspace, you must preface the task name with <code>apitooling.</code>.  When running the ant task directly, just the task name is required.  If the task name is incorrect, you will get the following error:
 +
<pre>/home/mrennie/workspaces/target/Project/build.xml:15: Problem: failed to create task or type apideprecation
 +
Cause: The name is undefined.</pre>
  
 
For documentation on task parameters and results see our [http://help.eclipse.org/helios/index.jsp?nav=/4_3_0 official documentation].
 
For documentation on task parameters and results see our [http://help.eclipse.org/helios/index.jsp?nav=/4_3_0 official documentation].

Revision as of 13:28, 24 November 2010

API Tools provides a number of tasks to integrate the tooling into your releng builds. They are available in the org.eclipse.pde.api.tools bundle. The jarred task code apitooling-ant.jar must be on the Ant classpath.

If you are running the tasks from an Eclipse target workspace, you must preface the task name with apitooling.. When running the ant task directly, just the task name is required. If the task name is incorrect, you will get the following error:

/home/mrennie/workspaces/target/Project/build.xml:15: Problem: failed to create task or type apideprecation
Cause: The name is undefined.

For documentation on task parameters and results see our official documentation.

Analysis

Official Documentation

This task runs a complete API analysis of an API profile relative to a baseline - including API use, binary compatibility, and bundle version number validation. The profile is the current state of a product under development. The profile is compared to an API baseline for binary compatibility (usually the previous release of a product).

The analysis does not include @since tag validation as all verification is performed on binary class files (source is not analyzed).

Analysis Report Conversion - The report conversion task converts the XML reports created by the Analysis Ant task into an HTML report.

API Freeze

Official Documentation

This task identifies APIs that have been added, modified, or removed relative to an API baseline. This task is intended to validate no API changes occur after an API freeze.

API Freeze Report Conversion - The report conversion task converts the XML reports created by the API Freeze Ant task into an HTML report.

API Deprecation

Official Documentation

This task runs a complete API analysis of an API profile relative to a baseline - looking only for members (classes, fields, methods) that have been deprecated / un-deprecated. The profile is the current state of a product under development. The profile is compared to an API baseline for deprecation changes (usually the previous release of a product).

API Deprecation Report Conversion - The report conversion task converts the XML reports created by the API Deprecation Ant task into an HTML report.

<?xml version="1.0" encoding="UTF-8"?>
<project name="project" default="default">
  <property name="xml" value="/reports/deprecation/xml"/>
  <property name="html" value="/reports/deprecation/html"/>
  <property name="profile" value="/eclipse/eclipse/plugins"/>
  <property name="baseline" value="/eclipse/eclipse_3.6.2/plugins"/>
 
  <target name="default" description="description">
    <apideprecation
        baseline="${baseline}"
        profile="${profile}"
        report="${xml}"
        debug="true"
    />
    <apideprecation_reportconversion
    	xmlfile="${xml}"
    	htmlfile="${html}"
    	debug="true"
    />
    </target>
</project>

API Use

Official Documentation

This task runs a complete search of a given baseline to determine a producer-centric report of API usage.

The analysis does not include bundles that are not API Tools enabled.

API Use Report Conversion - The report conversion task converts the XML reports created by the API Use Ant task into an HTML report.

API Use Migration

Official Documentation

This task takes a given API use scan and tries to re-resolve it within a given candidate product release and reports any unresolved references.

API Use Migration Report Conversion - The report conversion task converts the XML reports created by the API Use Migration Ant task into an HTML report.

File Generation

This task runs to generate all files required by API Tooling inside a binary bundle. This task is run during the Eclipse builds or during the bundle export for all projects that have an API Tooling nature.

Right now, only the file called .api_description is created.

Official Documentation

Back to the top