Issue 47 in instinct: The failure property does not get set on failure, so failing builds pass

[codesite...@google.com]

Issue 47: The failure property does not get set on failure, so failing
builds pass
http://code.google.com/p/instinct/issues/detail?id=47

New issue report by jem.mawson:
What steps will reproduce the problem?
1. Create an ant build where the specification suite fails and a
failureproperty attribute is defined
2. Follow the instinct task with a failure task looking to the property in
step 1.
3. Execute the ant build.

What is the expected output? What do you see instead?
The build status should be failure. Instead, it is successful.

Issue attributes:
Status: Accepted
Owner: jem.mawson
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Status: Started

Comment #1 on issue 47 by jem.mawson: The failure property does not get set

on failure, so failing builds pass
http://code.google.com/p/instinct/issues/detail?id=47

(No comment was entered for this change.)

[codesite...@google.com]

Updates:
Status: Fixed

Comment #2 on issue 47 by jem.mawson: The failure property does not get set

on failure, so failing builds pass
http://code.google.com/p/instinct/issues/detail?id=47

The CommandLineRunner will now return an exit code which is interpreted by
the ant
task. The task will set failure if the success code (0) is not returned.
This is
close to the approach taken by the JunitAntTask.