Okay four more bits of information:
What you said about Rake made me go look around in my rails app and I
noticed:
lib/tasks/jasmine.rake
=================
begin
require 'jasmine'
load 'jasmine/tasks/jasmine.rake'
rescue LoadError
task :jasmine do
abort "Jasmine is not available. In order to run jasmine, you
must: (sudo) gem install jasmine"
end
end
The LoadError must be bombing out so I try this....
Under irb
========
uby-1.8.7-p330 :001 > require 'rubygems'
=> true
ruby-1.8.7-p330 :002 > require 'jasmine'
=> true
ruby-1.8.7-p330 :003 > load 'jasmine/tasks/jasmine.rake'
NoMethodError: undefined method `namespace' for #<Object:0x38950>
from /Users/johnferguson/.rvm/gems/ruby-1.8.7-p330/gems/
jasmine-1.0.2.1/lib/jasmine/tasks/jasmine.rake:1
from (irb):3:in `load'
from (irb):3
I also think that script/console is probably more "real" for Rails
but.....
Under script/console
================
require 'jasmine'
Gem::LoadError: can't activate rack (>= 1.1, runtime) for
["jasmine-1.0.2.1"], already activated rack-1.0.1 for
["actionpack-2.3.4", "rails-2.3.4"]
from /Users/j
Using your debugging suggestion for Rakefile:
===================================
Running it show jasmine is there......
jasmine (1.0.2.1)
Some loading in irb world breaks and in script/console world also
breaks..... something there. Not sure yet what.
Also, I am on Rails 2.3.4 and you are on at least 2.3.5. I may have
to upgrade anyway it is annoying getting warnings from the system
about :
gem_dependency.rb:119:Warning: Gem::Dependency#version_requirements is
deprecated and will be removed on or after August 2010. Use
#requirement
And being so far behind has possible risks. Given we are working on
Heroku we need to see what stack we can go to.
Again, thanks