Seems to be a good start. You will have your modules able to rebuild when one of its dependency has changed.
But you might have a few things to consider: 1. How to clean your local repository if required. 2. You might have some modules rebuild too often. For example if you have 3 modules A ,B and C. B depends on A. C depends on A and B. When A is rebuild, it should be better to wait that B is rebuild before rebuilding C. For the first point, having enough disk space, combined with an occasional clean and full rebuild might be a solution. For the second point (if you consider it is a problem), you might take some inspiration from the new veto modificationset. Gilles > -----Original Message----- > From: Tim Diggins [mailto:[EMAIL PROTECTED] > Sent: jeudi 3 mai 2007 11:36 > To: [email protected] > Subject: Re: IvyCruise replacement > > have been thinking about this and am wondering if the simplest thing > would actually be to make an ivy-wrapper around the modificationset - so > that ivy swallows all the modificationsets, and checks all the > (--local--) dependencies' modificationsets, and if there are any > modificationsets on those, then it returns a false - ie. there will only > a modificationset on a project once all of its dependencies have cleared > their modificationsets. > > what do you think? > > -- Tim > > > Tim Diggins wrote: > > Hi - > > I'm considering ivy as a mechanism to express and manage dependencies > > (currently only expressed in ant tasks), but as one of my main drivers > > is to fix my continuous-build problems, am wondering what people do > > who use ivy and cruisecontrol at present, given that ivycruise is > > apparently not active and not working with latest cruisecontrol? > > > > What do people do? > > * not use cruisecontrol? > > * live with the failures when things get built in the wrong order? > > * Use some other kind of modificationset and just update all > > dependencies each build? > > > > any perspectives helpful > > ] > > thanks > > > > Tim > > > > > > -- > > --------------- > Tim Diggins > http://www.red56.co.uk/people/tim
