Description of problem:
When commands specified in command hooks are run, if any command fails the process will be aborted and subsequent commands will not run. This may prevent some cleanup commands being run, leaving temporary files in the user's workspace.
An optional attribute should be available on <before> and <after> tags to specify that they should run regardless of prior failures so that temporary files can be cleaned up even if prior commands fail.
Frankly speaking, project maintainers are more likely to rely on shell or build scripts to accomplish same functionality.
This would be a very easy change, so I think it is worth implementing.
(In reply to Ding-Yi Chen from comment #1)
> Frankly speaking, project maintainers are more likely to rely on shell or
> build scripts to accomplish same functionality.
That is a reason not to have added command hooks, but it is not a reason not to make command hooks better. If we are maintaining the feature, making it more usable is part of maintenance.
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-344