- Documentation (trunk)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
Display a dependency tree on the console.
This is a post resolve task, with all the behaviour and attributes common to all post resolve tasks.
Please prefer the use of retrieve + standard ant path creation, which make your build more independent from ivy (once artifacts are properly retrieved, ivy is not required any more).
|showEvicted||specify if evicted modules should be printed||No. Defaults to false|
|conf||a comma separated list of the configurations to take in consideration in the dependency tree||No. Defaults to the configurations resolved by the last resolve call, or * if no resolve was explicitly called|
|haltonfailure||true to halt the build on ivy failure, false to continue||No. Defaults to true|
|validate||true to force ivy files validation against ivy.xsd, false to force no validation||No. Defaults to default ivy value (as configured in configuration file)|
|settingsRef||A reference to the ivy settings that must be used by this task (since 2.0)||No, 'ivy.instance' is taken by default.|
|overwrite||Overwrite the value of the property if it already exist (since 2.0). Before 2.0, the properties were always overwritten.||No, 'false' by default.|
ExampleSuppose we have two dependencies one called mydep in revision 2.0 and one called myotherdependency in revision 2.2.
mydep has a transitive dependency on mytransitivedependency in revision 2.2.
<dependencytree />will display the following tree in the console:
Dependency tree for foobar