[gobo-eiffel-develop] geant task 'geant' can now handle execution result

[Sven E. <sve...@we...>]

As requested the task 'geant' now is able to handle (or ignore) the
execution result by specifying the attribute 'exit_code_variable' (as it is done in task 'exec').

To ignore the result (e.g. for running several unittests) use it like this for example:

  ...
  <geant file="build.eant" target="${target}" dir="argument" exit_code_variable="dummy"/>
  ...

Having introduced an artificial bug in one of the tests for the argument library to test
the new behavior the output looks as follows:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...

# PASSED:     531 tests
# Failed:     0 test
# Aborted:    0 test
# Total:      531 tests (1836 assertions)

Testing xargument...
Preparing Test Cases
Compiling Test Cases
Running Test Cases

Test Summary for xargument

# Passed:     12 tests
# FAILED:     1 test
# Aborted:    0 test
# Total:      13 tests (74 assertions)

Test Results:
FAIL:  [AP_TEST_PARSER.test_make] has_no_options_in_basic
   expected: 9
   but  got: 0

BUILD FAILED!

Testing xlexical...
Preparing Test Cases
Compiling Test Cases
Running Test Cases

...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

As you can see there still is a BUILD FAILED message but the script continues it's
execution.

- Sven