configurations
Tag: configurations Parent: ivy-module
Container for configuration element. If this container is not present, it is assumed that the module has one public configuration called 'default'.
since 1.3 You can define a new default conf mapping on this container by specifying the defaultconfmapping attribute.
A default conf mapping is very similar to the defaultconf which can be set on the dependencies tag, but it has a slightly different behaviour.
The default conf mapping not only defines the conf mapping to use when no conf mapping is specified for a dependency in this ivy file, but it also modify the way ivy interprets conf mapping with no mapped conf. In this case, Ivy will look in the default conf mapping and use the conf mapping defined in the default conf mapping for the conf for which there is no mapped conf.
See examples on the dependency page.
since 1.4 You can activate a confmappingoverride mode for all configurations, in which case the extending configurations will override the mappings of the configurations they extend from. This is an advanced feature which should be used only if you understand its implication.
For a discussion about the origin of this feature see this thread.
Attributes
| Attribute | Description | Required |
|---|---|---|
| defaultconfmapping | the default conf mapping to use in this ivy file since 1.3 | No, defaults to no default conf mapping |
| confmappingoverride | true to activate configuration mapping override, false otherwise since 1.4 | No, defaults to false |
Child elements
| Element | Description | Cardinality |
|---|---|---|
| conf | declares a configuration of this module | 0..n |
| include | include configurations from another file | 0..n |
It took time, but I've tried
It took time, but I've tried to improve the example almost as suggested. Do you think it's better like that?
__________________________________
Xavier Hanin
Jayasoft team member
Much Better!
Thanks.
Don't know if this is the case for others since I have just scratched the surface of IVY. It took me a minute or two to understand that the third column was for the <dependency> elements, by comparing the notes of this page and that of dependency page.
Maybe it would make sense to move this table there (since two out of three columns are about that element), and put a reference link on this page?
Just a thought. The table itself looks very good.
It's especially because you
It's especially because you just scratched the surface of Ivy that your opinion is so interesting 
I've moved the table on the dependency page as suggested, I hope this will help other people scratching the surface like you.
Thanks a lot for your feedback!
__________________________________
Xavier Hanin
Jayasoft team member
Thanks!
Cool.
One last comment on this (I swear!), the link to example probably should point to the example right away. At least that was what I was expecting when I clicked on the link. (The link probably can be created on the text "example")
Nice job. Thanks a bunch.
Done. BTW, your comments are
Done.
BTW, your comments are really welcome, so feel free to comment again if you still have ideas to improve the doc
__________________________________
Xavier Hanin
Jayasoft team member
Example should be presented in tables
The examples are very nice, since the description is a little hard to read. I think it probably would be better if the example is presented in a talbe, with the first column as the ivy content, second as the equivalence without default and third as that with default value.