Current Problem
---------------

The current SVN update process involves two separate requests to the SVN
repository. The first request updates the workspace, while the second produces
the change log.

If the first request fails then the build is marked as failed and processing
ceases. However, if the change log request fails then the build continues and an
empty change log is created. This is leading to confusion amongst a some end
users as it is not obvious as to what changes are included in the build. The
exact changes can only be identified by examining the console output which
produces the output in attachment current-output.txt.

Proposed Solution
-----------------
The ideal solution would be for this scenario to be treated in the same way as a
failure to the workspace update, the result being a failed build. The attached
patch contains a minor modification to the SubversionChangeLogBuilder in order
to handle this scenario.

If this solution is considered by the community to be too harsh then I would
appreciate a compromise solution where the behaviour was configurable, giving
the end user the ultimate choice as to how to handle this failure scenario.