C, C# and Ivy - Publishing binaries and many supporting files

into a risk of stale files being used by subscribe builds (foo.h is deleted and published, but foo.h remains on the subscriber build workspace even after retrieve) What approach do you take to keep effort and cleanup risks low? Thanks Peter -- Peter Kahn citizenk...@gmail.com http://www.goog

Failure Handler - Catching a BuildException

hing I'm going about this the wrong way... system('ant full.build"); system("ant checklog"); Thanks for the help... -- Peter Kahn [EMAIL PROTECTED] | IM: [EMAIL PROTECTED], [EMAIL PROTECTED], skype: citizenkahn http://analogoustendencies.blogspot.com/