On 09/01/11 - 09:26:21AM, Jan Provaznik wrote:
On 09/01/2011 01:05 AM, Steve Linabery wrote:
> I'm unable to run 'cucumber' or 'rake spec' against conductor
> 1) Running 'cucumber' in the src directory gives me this:
> no such file to load -- cucumber/rails (LoadError)
> /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
> Before you send me to lmgtfy.com
, I'm wanting to know if any other aeolus
developers have hit this same error, and if so what was the workaround specific to our
codebase. Is this an error in conductor code itself or a problem with my environment?
> 2) Running 'rake spec' in the src directory results in no output to stdout
from the command, which exits immediately and with a clean exit status. Same if I run it
as 'rake --verbose spec'...no output whatsoever.
> Thank you, I now return to slowly hitting my head against my desk.
both errors are most probably caused by commented gems in :test group in
Gemfile. AFAIK Chris commented it because these gems were loaded even in
production mode (or something like this), but not sure about this and
didn't have time to look at this closer yet.
Yeah, that's exactly right. When I had them uncommented, they were always
being loaded. Simon Harris and I had a discussion about this about a month
ago, and he proposed a solution, but I don't think it was ever implemented.
Someone should look in the archives, pick that up, and fix it.