- Documentation (2.5.0-local-20170911195251)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
fixdeps task serializes transitively resolved dependencies into an
The dependencies declared in an
ivy.xml can be specified as range of revisions. And the transitive dependencies too. As new versions of modules can be added to the repository anytime, resolved versions of ranges can change over time. It is then safer to resolve a range once and stick with the resolved revision. This way a resolve process is highly reproducible.
It is especially useful in a very dynamic environment like the OSGi one.
In a multi project environment some dependencies still need to be maintained loose: the ones between the projects. These dependencies, as soon as they are declared in the original ivy.xml, can be kept from being fixed. In order to do so, use the inner element
The recommended setup is then to:
ivy-spec.xmlin your project which specifies the dependencies, with ranges if needed
have an Ant target which resolves the
fixdepsto generate an
ivy.xml. This target should then only be called after
ivy-spec.xmlis modified. The generated
ivy.xmlcan safely be shared in a version control repository (Git, Subversion, …).
make the entire build workflow based on the resolve of the generated
This is a post resolve task, with all the behaviour and attributes common to all post resolve tasks.
The location of the Ivy file to generate
declares a dependency to keep from being fixed, and keep its original declaration from the original ivy.xml
These elements takes two attributes:
Simple fix of some dependencies.
<ivy:fixdeps tofile="ivy-fixed.xml"> <keep org="com.acme" module="mymodule"/> </ivy:fixdeps>
Fix of the dependencies but keep the dependency on
com.acme#mymodule as defined in the original ivy.xml.