If a repository is stopped, missing, or it's config has changed (excludes etc), crucible should always make a best-effort attempt to display the details, and should never throw an excpetion. If we have stored content, we should ALWAYS serve it.

If the repository is stopped or deleted, reviews will display error "repository not available" even if you have store contents of file in review

Steps to reproduce

1) In Administration > Projects, ensure your project has Store the contents of files in reviews checked.
2) Create review and add files from fisheye repository to the review.
3) Stop the fisheye repository in Administration
4) Go back to the review and try to expand the files.

(Testing on trunk seems to show that this issue has been fixed, but would like it confirmed with a test added, so we do not have a regression).