integrity/integrity — pull request #126 by richmeyers (2011-10-11 16:26:27+00:00)
Title: Report actual exceptions when requires fail

Swallowing exceptions makes for some misleading problem reports. For example, when broach is installed on a system that does not use rubygems and one attempts to run tests, the result is:

% rake test:acceptance
(in /home/test1/integrity)
/usr/local/lib/ruby/vendor_ruby/1.8/dm-core.rb:26: warning: already initialized constant Mash
DataMapper::Sweatshop::Unique - ParseTree could not be loaded, anonymous uniques will not be allowed
Loaded suite /usr/local/lib/ruby/vendor_ruby/1.8/rake/rake_test_loader
Started
EEE...Install broach to use the Campfire notifier
rake aborted!
Command failed with status (1): [/usr/local/bin/ruby -I"lib:test" "/usr/loc...]

(See full trace by running task with --trace)

With attached patch applied:

% rake test:acceptance
(in /home/test1/integrity)
/usr/local/lib/ruby/vendor_ruby/1.8/dm-core.rb:26: warning: already initialized constant Mash
DataMapper::Sweatshop::Unique - ParseTree could not be loaded, anonymous uniques will not be allowed
Loaded suite /usr/local/lib/ruby/vendor_ruby/1.8/rake/rake_test_loader
Started
EEE...Install broach to use the Campfire notifier: LoadError: no such file to load -- rubygems
rake aborted!
Command failed with status (1): [/usr/local/bin/ruby -I"lib:test" "/usr/loc...]

(See full trace by running task with --trace)

True reason for failure is https://github.com/Manfred/broach/pull/6.