- Documentation (2.5.2)
- Release Notes
- Tutorials
- Reference
- Introduction
- System Properties
- 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
outputters
Tag: outputters
Defines a list of report outputters usable in Ivy.
A report outputter is used at the end of the resolve process to generate a report of how the resolve has been performed.
Two report outputters are registered by default:
-
a log report outputter (LogReportOutputter)
which produces the output on the console at the end of the resolve, which looks like this:
---------------------------------------------------------------------
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
| default | 1 | 1 | 0 | 0 || 1 | 1 |
---------------------------------------------------------------------
-
an xml report outputter (XmlReportOutputter)
which produces an XML report in the cache, which is mandatory for correct Ivy behaviour, since it’s that report which is used when you do a post resolve step in a separate build from the resolve itself. It’s also this XML report which is processed to generate all the different reports available in the report task.
The child tag used for the parser must be equal to a name of a report outputter type (added with the typedef
tag).
To see how to define your own report outputter see Extending Ivy documentation
Child elements
Element | Description | Cardinality |
---|---|---|
any report outputter |
adds a report outputter to the list of available ones |
0..n |