Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0-beta-1
-
None
-
None
Description
This has already been discussed several times on the mailing lists, we need to review how the settings are loaded in Ant to make it easier for users.
The last discussion I've found is:
http://www.nabble.com/ivy%3Aconfigure-and-ivy%3Asettings-again...-td13394480.html
In which I think the final accepted proposition was:
http://www.nabble.com/Re%3A-ivy%3Aconfigure-and-ivy%3Asettings-again...-p13417344.html
To sum it up here, the foreseen changes are:
- Use a task instead of a type for settings
- if no id is specified in a settings task then the default will be assigned. This default is of course the one used in any resolve or retrieve tasks without explicit ids.
- a new override attribute on the settings task determines what happens if an id is not unique. The override attribute can be one of "true | false | notallowed" with notallowed being the default. The meaning of this attribute should be:
- notallowed : an error is raised if a settings has already been defined with this id
- true : the current settings will take precedence over any previously defined setting with this id
- false : the current settings will not override a previously defined setting with this id