I don't think thats a feature of Ivy, more a feature of xooctory. The CI
server may parse the ivy.xml files and build a dependency tree from
this. So when your projects depends on a library and you build a new
version of the lib, all dependent projects get rebuild, too.
As i dont know xooctory, I dont know how it determines, what has
changed, but from hudson I know that you can e.g. pull a scm repository
(svn,cvs,..) regularly or start a build via the invocation of an URL.
But all this is part of the CI server, not Ivy.
- Stephan
bhatia schrieb:
On the xooctory site, I read this:
"leveraging Ivy to manage the dependencies between the modules, and rebuild
exactly what is necessary, in the correct order, blocking builds when a
dependency is currently building, and so on"
Can someone provide more inputs/ideas on how to rebuild exactly what is
necessary using Ivy ? What are the (best) practices you use to determine
what has changed ?
thanks
