Description Kevin McGuire 2009-05-19 17:36:39 EDT

3.5 RC1

In bug #272371 we changed how we handle errors during build.

However, as part of that we now wrap the actual exception in one that says, 
"Errors running builder <B> on project <P>".  To see what the actual triggering exception is you must get the details of the status.

Instead, I think we should make that new status a multi status, with the original exception as a child status.  So if the error was "Assertion failed" then the log would look like:

  Errors occurred during build
    Errors running builder <B> on project <P>
      Assertion Failed


That way, it's clear what the real problem was, as well as the context.