report

Generates reports of dependency resolving. One report per configuration is generated, but all reports generated together are hyperlinked one to each other.

This task should be used only after a call to resolve, even if the call was not done during the same ant build.In fact, this task uses xml report generated by resolve in cache. So if you call resolve on a module for a given configuration, you can call report safely on this module and this configuration as long as you do not clean your ivy cache.

If you want to have an idea of what reports look like, check this very simple example.The task also generates a graphml file which can be loaded with the free yEd graph editor.Then following a few simple steps you can obtain a graph like this one.

since 1.4

If a custom XSL is specified, it's possible to specify additional parameters to the stylesheet.

Attribute

Description

Required

todir

the directory to which reports should be generated

No, defaults to ${ivy.report.todir}, or execution directory if not defined

outputpattern

the generated report names pattern

No, defaults to ${ivy.report.output.pattern}, or [organisation]-[module]-[conf].[ext] if not defined