Code review request: enable Crystal on .class files

[GoogleCodeExporter]

Purpose of code changes on this branch:
- allow analyzing .class files (issue #26)
- propagate exceptions in unit tests (issue #24)

Note that problem markers don't work well on .class files: they'll be 
associated with workspace or surrounding archive.

UI changes are incomplete: Selecting .class files will work, but Crystal will 
ignore .class files contained in selected elements or in runs on all files.  
This is because the new preference for whether to include binary archives is 
currently always false.  Passing .class files (IClassFile objects) to Crystal 
programatically will work fine.

When reviewing my code changes, please focus on:
- User-visible interface changes (IRunCrystalCommand, ICrystalAnalysis)
- Code duplication (WorkspaceUtilities) that can be removed if we are confident 
this works

After the review, I'll merge this branch into:
/trunk

Original issue reported on code.google.com by kevin.bi...@gmail.com on 6 Mar 2011 at 3:41

[GoogleCodeExporter]

So...Why is this issue still alive? Thomas and I reviewed and entered comments 
a couple days ago....Kevin, did you get them?

Original comment by ciera.christopher on 18 Mar 2011 at 1:42

[GoogleCodeExporter]

Original comment by ciera.christopher on 18 Mar 2011 at 1:43

• Changed state: Accepted

[GoogleCodeExporter]

Didn't get any comments. Where are they? Google doesn't show anything in this 
review task

Original comment by kevin.bi...@gmail.com on 18 Mar 2011 at 4:59

[GoogleCodeExporter]

Merged and committed to HEAD (updated Crystal version to 3.5.0)

Original comment by kevin.bi...@gmail.com on 15 May 2011 at 4:43

• Changed state: Fixed