Closed paulelliott closed 13 years ago
FYI, this breaks specjour for me on some Linux machines (I have one that works without the environment task and one that doesn't). I get an error that the task environment is not defined. Honestly, I have no clue as to why that happens.
Reintroducing the environment task fixes it for me. You can avoid the warning by defining it this way:
Rake::Task.define_task(:environment) { }
Neat. I knew I wasn't completely insane when I added that task... What version of ruby/rails are the linux machines running?
So this is the one that's failing:
ruby 1.8.7 (2010-12-23 patchlevel 330) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.01
This is the one that's not:
ruby 1.8.7 (2011-12-28 MBARI 8/0x6770 on patchlevel 357) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2012.01
As far as I can tell, this is the only difference. Apart from that it's Rails 3.2.1. I can give you a Gemfile, if you think it will be helpful.
Also, would you want me to open a pull request?
I've added the commits from garmz to the examples branch. I hope to push a release soon.
Thanks!
Awesome, thanks!
I keep seeing this warning in my logs whenever I run specjour:
WARNING: Global access to Rake DSL methods is deprecated. Please include ... Rake::DSL into classes and modules which use the Rake DSL methods.
I just removed the task(:environment) line and both my project's test suite and the specjour test suite run fine.