<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -4,7 +4,7 @@
 
 begin
   gem 'ci_reporter'
-rescue
+rescue Gem::LoadError
   $: &lt;&lt; File.dirname(__FILE__) + &quot;/../lib&quot;
 end
 require 'ci/reporter/rake/rspec'</diff>
      <filename>tasks/ci_reporter.rake</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>57e3056f0d5facfd5ffe5fea4190f6aa4c891a74</id>
    </parent>
  </parents>
  <author>
    <name>Graeme Mathieson</name>
    <email>mathie@woss.name</email>
  </author>
  <url>http://github.com/nicksieger/ci_reporter/commit/509a989247a98b4545e5add1e4657fecd7f9ad00</url>
  <id>509a989247a98b4545e5add1e4657fecd7f9ad00</id>
  <committed-date>2009-04-24T10:37:58-07:00</committed-date>
  <authored-date>2009-04-24T04:37:27-07:00</authored-date>
  <message>Explicitly catch a gem load error.

Don't just have a generic rescue block.  By default, a paramater-less rescue clause will only catch exceptions that inherit from StandardError.  Gem::LoadError doesn't, which means it would never be caught by a blank rescue clause.

Signed-off-by: Nick Sieger &lt;nicksieger@gmail.com&gt;</message>
  <tree>8991f1c5fd92b5257f4851595e07a2be88e4634e</tree>
  <committer>
    <name>Nick Sieger</name>
    <email>nicksieger@gmail.com</email>
  </committer>
</commit>
