<hasNature>

Description

The hasNature condition is an Ant condition that can be used to check if a project has a specific nature. Natures are used to assign specific behaviour to Eclipse projects. Java projects for example have the nature 'org.eclipse.jdt.core.javanature'.

The hasNature condition can be used with ant's native condition and waitfor tasks (see Condition Task). It can also be used with the if-task from the ant-contrib project to create build steps that check whether a project has some specific nature.

Arguments

The hasNature datatype provides the following arguments:

Example usage

The following example checks if the project with the name 'simple.java.project' has the nature 'org.eclipse.jdt.core.javanature':

<antcontrib:if>
    <ant4eclipse:hasNature workspacedirectory="${workspace}"
                           projectname="simple.java.project"
                           nature="org.eclipse.jdt.core.javanature" />
   <antcontrib:then>
     ...
   </antcontrib:then>
 </antcontrib:if>

<hasBuildCommand>

Description

The hasBuildCommand condition is an Ant condition that can be used to check if an Eclipse project has a specific build command. An Eclipse project can have several build command assigned to it. Those build commands are normally executed after a file has been saved (incremental build) or when a full build is initiated (Project -> Clean...) (manual build). A typical java project contains the org.eclipse.jdt.core.javabuilder which invokes the default Eclipse compiler on java sources.

If you would like to write build steps that depend on specific build commands, you can use the hasBuildCommand condition which checks if a project has a specified buildCommand. The hasBuildCommand-condition can be used with ant's native condition and waitfor tasks (see Condition Task). It can also be used with the if-task from the ant-contrib project to create build steps that check whether some specific build commands exist or not.

Arguments

The hasBuildCommand datatype provides the following arguments:

Example usage

The following example checks if the project with the name 'simple.java.project' has the build command 'org.eclipse.jdt.core.javabuilder':

<antcontrib:if>
  <ant4eclipse:hasBuildCommand workspacedirectory="${workspace}"
                               projectname="simple.java.project"
                               buildcommand="org.eclipse.jdt.core.javabuilder" />
  <antcontrib:then>
    ...
  </antcontrib:then>
</antcontrib:if>

<executeBuildCommands>

Description

The executeBuildCommands task allows you to iterate over one or more build commands that are defined in your eclipse project.

Arguments

The executeBuildCommands task provides the following arguments:

Example usage

The following example iterates over all build commands defined in the eclipse project 'simple.java.project':

<ant4eclipse:executeBuildCommands workspacedirectory="${workspace}"
			          projectname="simple.java.project">
 
	<org.eclipse.jdt.core.javabuilder>
		...
	</org.eclipse.jdt.core.javabuilder>
</ant4eclipse:executeBuildCommands>

<getProjectDirectory>

Description

Returns the project directory for a given eclipse project. Since ant4eclipse supports the usage of linked projects, it is necessary in some case to resolve the 'real' path of a project.

Arguments

The getProjectDirectory task provides the following arguments:

Example usage

The following example resolves the absolute path of the the project with the name 'simple.java.project':

<ant4eclipse:getProjectDirectory workspacedirectory="${workspace}"
                                 projectname="simple.java.project"
	                         property="test" />

<workspaceDefinition>

Description

The workspaceDefinition type allows you define a workspace with a custom workspace layout. In eclipse a workspace always has a flat layout (Workspace -> Projects), but many users store there eclipse projects in a hierarchical way within the source code repository. Ant4eclipse directly supports the usage of custom workspace layouts through this datatype.

Many thanks to Mark Riley for submitting the initial patch!

Arguments

The workspaceDefinition datatype provides the following arguments:

Nested Elements

To define a custom workspace layout, you can use one or more nested Directory Sets.

Example usage

The following example defines a workspace that contains projects that can be found in any sub-directory (recursively) of the directory 'D:/tmp':

  <ant4eclipse:workspaceDefinition id="myWorkspace">
    <dirset dir="D:/tmp">
      <include name="**"/>
    </dirset>
  </ant4eclipse:workspaceDefinition>

You can use the workspace definition within the ant4eclipse task by using the 'workspaceId' attribute insead of the 'workspaceDirectory' attribute.

<linkedResourceVariable>

Description

The linkedResourceVariable datatype is an Ant datatype that allows you to specify an environment specific path for a linked resource. Within the eclipse IDE these variables are defined in the preferences dialog (Window -> Preferences..., General -> Workspace -> Linked Resources).

Arguments

The linkedResourceVariable type provides the following arguments:

Usage examples

<ant4eclipse:linkedResourceVariable name="myLinkedResourcesDirectory" location="D:/location" />