[EMAIL PROTECTED] wrote:
I must admit that this area seems to be a real shortcoming in existing ANT tasks - not being able to reliably swallow errors in subtasks, whatever they may be.
You have to remember that Ant is designed to be a build tool, first and foremost, not a generic workflow system. It is only later, as things like deployment get involved, that you do start thinking about fault handling, cleanup etc.
And in most builds, a simple "build failed" response is exactly right. The build failed: something didn't work.
Many tasks have failonerror attributes, but that is still fairly simple error handling, it is "ignore specific errors here"; not real fault handling at all.
1. you can use <available> to search a path (eg. env.Path and env.PATH) for an executable. You need to include the .exe extension for windows, assuming is an executable.
2. try/catch from ant-contrib will catch faults and let you handle them properly.
-steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
