- 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
manager
Tag: manager Parent: conflicts
(since 2.0) the conflicts section is deprecated. Use conflict instead.
Specify a conflict manager for one or several dependencies.
The way to specify a conflict manager is by giving indication to which dependencies the conflict manager applies (by giving organisation and module names or name regexp), and then specifying the conflict manager, either by giving its name or by specifying a fixed revision list, in which case a fixed conflict manager is used.
See Conflict Manager for details on conflict managers in general.
Attributes
| Attribute | Description | Required |
|---|---|---|
org |
the name, or an expression matching the name of organisation to which this conflict manager should apply (see |
No, defaults to |
module |
the name, or an expression matching the name of module to which this conflict manager should apply (see |
No, defaults to |
name |
the name of the conflict manager to use |
Exactly one of two |
rev |
a comma separated list of revisions this conflict manager should select |
|
matcher |
the matcher to use to match the modules for which the conflict manager should be used (since 1.3) |
No, defaults to |