- 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
Reference
Welcome to the Ivy reference documentation!
If you don’t know Ivy at all, take a look at its features, the faq and the tutorials before digging into this reference documentation.
Reference Overview
This documentation is broken into several parts:
-
Introduction
-
This part gives you the meaning of some words used all over the Ivy documentation, such as organization, module, configurations, settings, …
-
This part introduces the main concepts used in Ivy: dependency resolvers, variables, patterns, and explains a central Ivy concept: module configurations.
-
As the title suggests, here you will find an explanation of how Ivy does work internally, which can help to better understand and customize its use.
-
This part describes how to install Ivy.
-
This part describes possibility to control the behavior of Ivy at run time
-
-
This part is dedicated to the specification of the settings file of Ivy (usually called ivysettings.xml). It also gives the list of built-in dependency resolvers available in Ivy.
-
This part is the reference for the module descriptors, the Ivy files in which you describe your dependencies. If you have any questions about what can be done or not in an Ivy file, you will find the answer here.
-
This part describes how to use Ivy from Ant. It’s in this section that all Ant tasks provided by Ivy are specified.
-
Even though Ivy is most often used from Ant, it can also be used from the command line. This page describes how you can do this.