- Documentation (2.5.0-rc1)
- Release Notes
- Tutorials
- Reference
- Introduction
- Settings Files
- Ivy Files
- Ant Tasks
- artifactproperty
- artifactreport
- buildlist
- buildnumber
- buildobr
- cachefileset
- cachepath
- checkdepsupdate
- cleancache
- configure
- convertmanifest
- convertpom
- deliver
- dependencytree
- findrevision
- fixdeps
- info
- install
- listmodules
- makepom
- post resolve tasks
- publish
- report
- repreport
- resolve
- resources
- retrieve
- settings
- var
- Using standalone
- OSGi
- Developer doc
dependencies
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 dependencies 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.
(since 2.2) Attributes defaultconf and defaultconfmapping can be used together. In earlier versions, if both defaultconf and defaultconfmapping are defined, it’s the defaultconfmapping that is used.
(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.
(since 2.5) Attributes inherited via extends are added to dependencies only on delivery and override attributes inherited from configurations.
Attributes
| Attribute | Description | Required |
|---|---|---|
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 |
confmappingoverride |
|
No, defaults to |
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 |
0..n |
|
excludes artifacts, modules or whole organizations from the set of dependencies of this module (since 2.0) |
0..n |
|
specifies an override mediation rule, overriding the revision and/or branch requested for a transitive dependency (since 2.0) |
0..n |
|
specifies a conflict manager for one or several dependencies (since 2.0) |
0..n |