Description
Easyant uses two ivy instances:
- one for easyant itself to resolve buildtypes / plugins / skeletons
- one for projects to resolve dependencies
Currently, easyant ivy instance can only be configured through easyant-conf.xml
<easyant-config> <ivysettings file="${easyant.home}/ivysettings.xml"/> </easyant-config>
This can make things complex when dealing with multiple ivysettings.xml.
To enhance this i suggest to introduce :
- a user ivysettings.xml (by default ${user.home}/.easyant/easyant-ivysettings.xml but can be configured through a property say user.easyant.ivysettings.file)
- a global ivysettings.xml (by default ${easyant.home}/easyant-ivysettings.xml but still configurable through a property say global.easyant.ivysettings.file)
If no user's ivysettings file is found, we will check the global one, if still not found we will use an easyant-ivysettings.xml shipped inside easyant-core.jar.
As i'm not sure we need to break old way to configure easyant ivy instance (through easyant-conf.xml) i suggest to consider the configured file as a global settings.