EasyAnt configuration file

The configuration file named easyant-conf.xml allow you to tune :

easyant ivy instance (used to retrieve build types / plugins)
system plugins
properties

<easyant-config>
        <!-- Configure the easyant ivy instance -->
    <ivysettings file="${easyant.home}/ivysettings.xml"/>
        <!-- Configure system plugins -->
    <system-plugins>
        <plugin organisation="org.apache.easyant.plugins" module="skeleton" revision="0.1" as="skeleton"/>
        <plugin organisation="org.apache.easyant.plugins" module="ivy-repo-management" revision="0.1" as="repo-management"/>
    </system-plugins>
        <!-- Configuring user properties -->
        <properties>
            <property name="my.property" value="foobar"/>
        </properties>
</easyant-config>

Configuring easyant ivy instance

By default, easyant ivy instance is configured to use a set of repositories based on your file system that are deployed with the easyant distribution.

Easyant ivy instance is not used to retrieve project dependencies.
If you want to configure the project ivy instance you should look at this page.

You can configure / override the easyant ivy instance through the following tag

<ivysettings file="/path/to/ivysettings.xml"/>

<ivysettings url="/path/to/ivysettings.xml"/>

attribute name	description
file	a file referecing a ivysettings file for easyant ivy instance
url	an url referencing a ivysettings file for easyant ivy instance

Configuring system plugins

A system plugin can provide some additionnal functionnalities that can be used from everywhere.
To reference a set of plugins you can use the following syntax :

<plugin organisation="org.apache.easyant.plugins" module="skeleton" revision="0.1" as="skeleton"/>

Plugin attributes

attribute name	description
organisation	plugin organisation name
org	shorter form to set plugin organisation name
module	plugin module name
module	plugin module name
revision	plugin revision number
rev	shorter form to define plugin revision number
mrid	a module revision id. This argument can be used to define a plugin using a module revision id (Syntax: [organisation]#[module];[revision])
as	an alias to prefix plugin's targets
mandatory	plugin module name
mode	define if we should import or include the plugin

<!-- Using exploded style -->
<plugin organisation="org.apache.easyant.plugins" module="skeleton" revision="0.1" as="skeleton"/>
<!-- shorter form -->
<plugin org="org.apache.easyant.plugins" module="skeleton" rev="0.1" as="skeleton"/>
<!-- Using a mrid style -->
<plugin mrid="org.apache.easyant.plugins#skeleton;0.1" as="skeleton"/>

Defining user properties

You can also define user properties. Those properties will be available from everywhere when invoking easyant.

<property name="my.property" value="foobar"/>
<property file="/path/to/mycompany.properties"/>
<property url="/path/to/mycompany.properties"/>

Properties attribute