On 1/9/07, Stephane Bailliez <[EMAIL PROTECTED]> wrote:
Xavier Hanin wrote: > > What you do is what we call in Ivy "changing" revisions. If you configure > Ivy properly, you should be able to let Ivy do its cache management > itself, > with no need to do a manual clean up. Then you will only download what > has What is 'configured properly' in this case ?
you can either declare changing dependency one by one in your Ivy files, using changing="true" on your dependency, or declare a changing pattern in your ivyconf.xml, to say that all versions containing dev should be considered changing, for instance. Does it answer the question? Xavier
actually changed, which could improve your build significantly. > Moreover, if > your frequent builds are done on your CI system, maybe you can use > useOrigin="true" on the CI system, so that the copy to the cache can be > avoided. Does it make sense in your situation? -- stephane
