Improve console batch mode

[gramian]

What does this PR do?

Overall, this change alters the console behavior such that if an error occurs in batch mode or during a script, execution is halted and if in batch mode, the console is exited.

In particular these changes are introduced in Console.java:

1. Make parse method have 3 arguments (see line 731). The third argument is a boolean indicating batch mode, which is true by default.
2. Add wrapper method with 2 arguments to minimize changes (see line 727)
3. New parse does not consume exeception anymore, but throws them upwards (see line 742ff).
4. "Lower" execute method now throws also RuntimeExeception (see line line 223)
5. "Upper" execute method uses new parse method depending on if batch mode is set.

Motivation

Currently console continues to execute commands in scripts or batch even though previous command fails. This can produce unwanted results. Especially tracking errors is complicated since if the last line passes, it seems as if a script or batch is successful.

Additional Notes

@lvca

• ConsoleTest: testNotNullProperties fails, is this test faulty?
• Need help constructing tests for this.
• The "upper" execute method (line 155) should be renamed so there are not two methods names execute.
• Are the exeception-related changes OK?

Checklist

• I have run the build using mvn clean package command
• My unit tests cover both failure and success scenarios

[robfrank]

I reworked a bit this pr.
now the console has a new flag -fae (fail at end) that is evaulated only when using the batch mode.
If batch mode is enabled:

• if -fae is added, the whole batch is executed and errors are just printed out
• otherwise the batch is stopped when an error occurred

[gramian]

This looks good; I will test this later today. Did you see the "Additional Notes" above?

Thanks for the improvements!

PS: I will make additions to the docs once this PR is merged.

[robfrank]

@gramian All the tests are green and I adde a couple of tests in ConsoleBatchTest to verify the new flags. My intention was to not change the previous behavior.

[gramian]

@robfrank If I remember correctly, the testNotNullProperties console test did not actually run, but I will check this again later.

[gramian]

I figured it out. The test runs and seems to work as it is supposed to.

[gramian]

I tested with a simple script and it seems to work as expected.