- Documentation (2.5.0-rc1)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
Tag: include Parent: configurations
Include configurations specified in another file.
The included file should have a
configurations tag as root tag, which follow the same specification as the configurations tag of the Ivy file.
This means that it can contain conf declarations, other file inclusions, and have attributes controlling conf mapping.
When delivering an Ivy file with such an inclusion, the included descriptor file is inlined, i.e. Ivy removes the dependency on the external file.
[since 2.5] Attributes inherited through included file are set on
dependencies element due to the way module descriptor updater works currently.
the file to include
<ivy-module version="1.0"> <info organisation="myorg" module="mymodule"/> <configurations> <include file="path/to/included-configurations.xml"/> <conf name="conf3"/> </configurations> <dependencies> <dependency name="mymodule1" rev="1.0"/> <dependency name="mymodule2" rev="2.0" conf="conf2,conf3->*"/> </dependencies> </ivy-module>
included-configurations.xml like this:
<configurations defaultconfmapping="*->@"> <conf name="conf1" visibility="public"/> <conf name="conf2" visibility="private"/> </configurations>
Defines 3 configurations,
mymodule1 is required in each configuration, with for each the same configuration (
conf1 is needed in
conf3) due to the
defaultconfmapping defined in the included file.