Closed inspector-cochise closed 12 years ago
this requires a clear distinction between ui and exception handling (when to catch what exception)
Actually my above comment doesn't really hit the issue. But it shows another problem in error and failure handling. I will open a milestone for the error handling.
I invented a new method UserCommunicator.reportError(Exception e) It passes the exception to FormattedConsole wich prints it nicely formatted fitting into the indentation schema.
Maybe for now this issue is done. Logfiles would only help for debugging. (Not the user to solve the problem)
For now:
That should have solved this vague issue.
especially in the html report
the relevant method (to implement) is public void UserCommunicator.reportError(String error)