My configuration is including ":lib => 'will_paginate'", so try like
this,
config.gem "will_paginate", :version => "~> 2.3.11", :lib =>
'will_paginate', :source => "http://gemcutter.org"
It must be specified in here,
Rails::Initializer.run do |config|
config.gem "will_paginate", :version => "~> 2.3.11", :lib =>
'will_paginate', :source => "http://gemcutter.org"
end
I have a very annoying problem, when doing rake db:migrate, I get the
error message:
Missing these required gems:
will_paginate ~> 2.3.11
But the gem is not missing, It runs very well in my app. To make the
rake pass I have to comment out the gem in my environment.rb file.
Is it possible that rake is from one install of ruby and but that when
you run your app a different install is used ? (compare the output of
which ruby and which rake)
Jonas-MB:stuteri jeb$ which ruby
/opt/local/bin/ruby
Jonas-MB:stuteri jeb$ which rake
/usr/bin/rake
Is that not as is should? Everything else works fine...
That means you have two installs of ruby, one which has your gems
installed, one which doesn't. Does /opt/local/bin/rake exist ? if not,
install it (be careful that you may have the same problem with the gem
command - check what which gem says)
I guess this happened when I upgraded to snow leopard. My .profile
file was last modified under 10.5. It looks like:
# MacPorts Installer addition on 2009-02-11_at_21:01:31: adding an
appropriate PATH variable for use with MacPorts.
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
# Finished adapting your PATH environment variable for use with
MacPorts.
I guess this happened when I upgraded to snow leopard. My .profile
file was last modified under 10.5. It looks like:
# MacPorts Installer addition on 2009-02-11_at_21:01:31: adding an
appropriate PATH variable for use with MacPorts.
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
# Finished adapting your PATH environment variable for use with
MacPorts.
Is that the problem?
What is the easiest way to clean this mess up?
It depends whether you want the macports install of ruby or whether
you'd rather keep the non macports one (if you don't care about the
macports one then you should be able to get macports to remove it. If
you do want it, the easiest thing might be to force macports to
reinstall it or something like that)
I've had this problem before on Leopard. The only way that I've been
able to get rid of that warning was to remove :version from the
options hash. So this:
I realize that this is not a true solution, but the gem version isn't
required unless you think you may be using a different version in your
production environment. But, technically speaking, you should have a
mirrored environment for your development and production machines
anyway.
It is a strange error that I've mentioned on here before. Try the
method above and see if that helps.