Ivy configuration

In order to work as you want, EasyAnt sometimes need some settings. Actually, EasyAnt can work with no specific settings at all, see the default settings documentation for details about that. Ivy is able to work in very different contexts. You just have to configure it properly.

Settings are specified through an xml file, usually called ivysettings.xml.
Here is an example of settings file :
<properties file="${ivy.settings.dir}/ivysettings-file.properties" />
<settings defaultCache="${cache.dir}" defaultResolver="ibiblio" checkUpToDate="false" />
<ibiblio name="ibiblio" />
<filesystem name="internal">
<ivy pattern="${repository.dir}/[module]/ivy-[revision].xml" />
<artifact pattern="${repository.dir}/[module]/[artifact]-[revision].[ext]" />
<module organisation="jayasoft" name=".*" resolver="internal" />
Mainly, the settings enable to configure the default cache directory used by ivy and the dependency resolvers that it will use to resolve dependencies.
Note: To work, this settings file needs a property file named ivysettings-file.properties in the same directory as the settings file, with ivy variables you want in it.
If you want to have more details on this settings file we strongly recommend you to read the reference documentation of settings file

EasyAnt uses two ivy instance :
  1. used to resolve/retrieve EasyAnt modules (which can be buildtypes/ plugins or skeletons) dependencies
  2. used to resolve/retrieve project dependencies
There is a strong separation of context, this means that plugins dependencies will not be polluting your project.
Both instance are configurable.

Project ivy instance

The project ivy instance is in charge to configure ivy for your project (configure repositories used to retrieve your projects dependencies for example).

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).