/Users/me/.rvm/gems/ree-1.8.7-2011.03@evokat25/gems/activesupport-2.3.8/lib/active_suppor开发者_C百科t/dependencies.rb:105:in `const_missing\':NameError: uninitialized constant Rails::Initializer::Pap
I have no idea why I am getting this? $ which rake /Users/kamilski81/.rvm/gems/ruby-1.9.2-p290@depot/bin/rake
sass .CSS compilation fails on one machine, but works on the other. Using Sass gem version 3.1.7 on both w/Bundler.
I\'m trying to create custom generator for Rails 3.1. And I wrote this: module SomeGem module Generators
The following error shows up in my Glassfish log when attempting to access my app: Caused by: org.jruby.exceptions.RaiseException: (NameError) method \'to_yaml\' not defi开发者_如何学编程ned in Objec
Bundler keeps install sqlite3 every time, but i\'m not using it in my project. I\'ve chosen Postgres, but can not deploy it to Heroku. Bundler is the reason for that. Why it is? And what should i do?
When I try to deploy to my newly set up server, capistrano throws this at me. *** [err :: fupifarvandet.dk] fatal: Could not parse object \'22e2458b7751开发者_开发百科9e8eb8463170c1a1fe4bab105f3e\'.
After running the bundle install command, \'Gemfile.lock\' is created in the working directory. What do the directives inside that file mean?
I\'m trying to install a gem, meta_search-1.1.0.pre2. The gem\'s spec, bundler, and rubygems each report/install different dependency version requirements.
EDIT: I\'m an idiot -- I figured out the problem. In a gem I had written a while back, I had VERSION=\'0.0.1\', and for some reason that overrode the version number of bundler.