[
https://issues.apache.org/jira/browse/IVY-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-438.
------------------------------
Resolution: Fixed
I've refactored the code and updated the doc to reflect the change.
Settings files now look like that:
{code:xml}
<ivysettings>
<settings defaultCache="/path/to/my/cache"/>
...
</ivysettings>
{code}
Old element names (ivyconf and conf) are still supported but deprecated.
> Rename ivy configuration in settings to remove ambiguity on configuration
> meaning
> ---------------------------------------------------------------------------------
>
> Key: IVY-438
> URL: https://issues.apache.org/jira/browse/IVY-438
> Project: Ivy
> Issue Type: Improvement
> Affects Versions: 1.4.1
> Reporter: Xavier Hanin
> Assigned To: Xavier Hanin
> Fix For: 1.5
>
>
> Since its inception Ivy suffers from an ambiguity on the meaning of
> configuration. Indeed configuration is used both for the act of configuring
> Ivy, with a configuration file used for that, and for module configurations,
> which can be thought as ways to use a module.
> The proposition is to remove this ambiguity by renaming the configuration
> file in a settings file.
> This is mostly a modification in the documentation, but will also impact the
> code, the default name for settings file being now ivysettings.xml instead of
> ivyconf.xml, and the root element being ivysettings instead of ivyconf.
> ivyconf element will still be recognized but deprecated. ivyconf.xml will
> still be found in the working directory, but ignored if an ivysettings.xml
> exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
