Skip to Content
Scope: PDE Projects

Description

This macro builds an eclipse feature project. It reads the information from the file feature.xml and builds the feature according to these settings.

Important: This task is implemented as an Ant macro. To use this task, you have to import the file 'a4e-pde-macros.xml' in your build file.

Arguments

The buildFeature task provides the following arguments:

Argument Description Required
workspaceDirectory Absolute path of the workspace directory Either 'workspaceDirectory' or 'workspaceId' has to be specified
workspaceId The identifier of a defined workspace (see <workspaceDefinition>) Either 'workspaceDirectory' or 'workspaceId' has to be specified
projectName Name of the eclipse project Either projectName or featureId (and optional featureVersion) has to be set
featureId The id of the feature Either projectName or featureId (and optional featureVersion) has to be set
featureVersion The version of the feature Either projectName or featureId (and optional featureVersion) has to be set (default: 0.0.0).
targetPlatformId The id of the target platform. yes
platformConfigurationId The id of the platform configuration (for cross platform builds). no
destination Name of the directory that will contain the plugin after building (same as the 'Destination directory' in the PDE-Export wizardin Eclipse). The plugin will be built in to <destination>/plugins/<Bundle-SymbolicName>_<Bundle-Version>.jar. yes
clearDestination If set to true the content of the destination directory will be deleted before building the feature. no (default: false)
skipBuildFeature If set to true the feature itself will not be built. In this case the macro only builds the defined plugins. no (default: false)
packageAsJar If set to true the feature will be packaged as a jar file. no (default: true)
packagePluginsAsJar If set to true the contained plug-ins will be packaged as jar files. no (default: true)
packagePluginSourcesAsJar If set to true the sources of the contained plug-ins will be build and packaged as jar files. no (default: true)
defaultCompilerOptionsFile Absolute path to an eclipsed compiler options file that is used as the default compiler options file if no project specific file exists. no
cleanPluginBuild Indicates that the output folders of the nested plugin projects should be cleaned prior building. no (default: true)
useEcj Enables or disables the use of the ecj compiler as the backend. no, default to true

Example usage

The following example builds the feature project with the project name 'test.feature'. The built feature will reside in 'd:/plugins'.

<buildFeature workspaceDirectory="${workspace}"
              projectName="test.feature"
              targetplatformid="target.platform"
              destination="d:/plugins" />