<targetPlatform>
Description
The targetPlatform type can be used to define a target platform that may
consist of more than one directory.
Target platforms are used when working with plugin and feature-projects. They define locations where dependent, binary, plugins can be found. A valid target platform for example can be an Eclipse installation.
The directories listed in the targetPlatform type must be the parent directory
of the plugins directory, that contains the plugins. Example: if you would like to
include the plugins of your eclipse distribution, you would add "c:/eclipse" (or whereever you've
installed Eclipse) as a directory and not "c:/eclipse/plugins".
To use a target platform defintion with one of ant4eclipse tasks, you'll specify a targetPlatform
nested element in your task. You can either define a complete target platform their or you can
reference a defintion created before using the refid attribute.
Arguments
| Argument | Description | Required |
|---|---|---|
| id | An id that can be used to reference this platform definition later in your buildfile | no |
| refid | Specifies a reference to a target platform defined before | no |
Parameters specified as nested elements
location
Each directory you want to include in your platform definition must be added using a location element.
| Argument | Description | Required |
|---|---|---|
| dir | The directory that should be added to your platform definition. Inside this directory there must be
the plugins directory that contain the plugins |
yes |
Example
This creates a target platform defintion that consists of three directories. The defintion
can be referenced via it's id eclipse-3.2-full
This example uses the same target platform definition directly in the buildPlugin-task: