Simon Laws (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TUSCANY-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731675#action_12731675 ]
Simon Laws commented on TUSCANY-3151:
-------------------------------------
While it's ok to aggregate warnings we should switch to stopping on the first error we find.
I don't understand why this would be better than reporting multiple
errors before stopping processing.
The only reason I can see for stopping processing on the first error
would be that the internal runtime state is so damaged that it's
impossible to continue processing. For some errors, this may be
the case. For other errors, it is possible to maintain the
tuntime's internal consistency and continue processing, and I don't
think Tuscany should abort further processing and error reporting
in these cases.
The benefit of accumulating and reporting multiple errors is that
it allows more than one error to be found and fixed in a single
test run. This can be compared with the ability of a compiler to
report multiple source errors in a single compilation. I think most
people would expect this from a modern compiler.
Am I missing something? What is the benefit to users of making
this change?
Simon
Don't accumulate severe errors
------------------------------
Key: TUSCANY-3151
URL: https://issues.apache.org/jira/browse/TUSCANY-3151
Project: Tuscany
Issue Type: Sub-task
Reporter: Simon Laws
