- Documentation (2.3.0)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
Tag: dependencies Parent: ivy-module
Container for dependency elements, used to describe the dependencies of this module.
If this container is not present, it is assumed that the module has no dependency at all.
This container provides for two similar behaviors. An overview is given here. (See configurations doc page for more details about these behaviors).
defaultconfDefines the conf attribute to use when no conf is defined for a dependency in this ivy file. It is only used when no conf mapping is defined, and has no influence in other cases.
defaultconfmappingInfluences the way that a conf mapping with no mapped conf is interpreted.
In Ivy 2.1.0 and earlier, if both defaultconf and defaultconfmapping are defined, it's the defaultconfmapping that is used. Since Ivy 2.2.0, these attributes can be used together.
|defaultconf||the default configuration to use when none is specified in a dependency. since 1.1||No, defaults to *->*|
|defaultconfmapping||the default configuration mapping to use in this ivy file. since 1.3||No, defaults to no default conf mapping|
|dependency||declares a dependency for this module||0..n|
|exclude||excludes artifacts, modules or whole organizations from the set of dependencies of this module since 2.0||0..n|
|override||specify an override mediation rule, overriding the revision and/or branch requested for a transitive dependency since 2.0||0..n|
|conflict||specify a a conflict manager for one or several dependencies since 2.0||0..n|