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 two similar behaviors described below. (See configurations doc page for more details about these behaviors).

since 1.1 defaultconf defines 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.

since 1.3 defaultconfmapping influences 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.


Attribute Description Required


the default configuration to use when none is specified in a dependency. since 1.1

No, defaults to *->*


the default configuration mapping to use in this Ivy file. since 1.3

No, defaults to no default conf mapping

Child elements

Note: as specified by the ivy.xsd, the children elements are ordered; first must come the dependency elements, then the exclude elements, then the override elements, and then the conflict elements.

Element Description Cardinality


declares a dependency for this module



excludes artifacts, modules or whole organizations from the set of dependencies of this module since 2.0



specifies an override mediation rule, overriding the revision and/or branch requested for a transitive dependency since 2.0



specifies a conflict manager for one or several dependencies since 2.0