EasyAnt ivy instance

EasyAnt ivy instance is in charge to configure ivy for easyant internal use (configure repositories used to retrieve buildtypes/plugins/skeletons for example).

By default easyant ivy instance is configured to use the default ivysettings provided by easyant-core.jar.

Lookup mechanism

To configure EasyAnt ivy instance use a lookup mechanism. It will:

User location

User default location can be configured through user.easyant.ivysettings.file property.

Example :
> easyant -Duser.easyant.ivysettings.file=/path/to/ivysettings.xml
You can tell easyant to ignore user location by setting ignore.user.ivysettings property to true.

Example :
> easyant -Dignore.user.ivysettings=true

Global location

User default location can be configured through global.easyant.ivysettings.file property.
> easyant -Dglobal.easyant.ivysettings.file=/path/to/global/ivysettings.xml

default ivy settings provided by easyant-core.jar

You can reference this default ivysettings file through the property easyant.default.ivysettings.url.
This file preconfigure :
apache-easyant-plugins repository base url is accessible through apache.easyant.public.url property.

Extending the default configuration

In enterprise context it can make sense to configure an enteprise repository to store easyant plugins/ easyant skeletons etc...

This can be done writting your own ivysettings including if necessary the default configuration :
<!-- import the default ivy settings -->
<include url="${easyant.default.ivysettings.url}"/>
<!-- define your own default resolver, here a chain that include a new repo + the default chain provided by easyant -->
<settings defaultResolver="my-chain"/>
<filesystem name="my-custom-repo">
<ivy pattern="/path/to/your/repo/[organisation]/[module]/ivy-[revision].xml"/>
<artifact pattern="/path/to/your/repo/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/>

<chain name="my-chain">
<resolver ref="my-custom-repo" />
<resolver ref="easyant-default-chain" />