If I have a gem locally that I change without updating the version number the bundler never seems to notice.
I have a gem fx 'devise-assistant' version 0.1.0. If I add a single method and run 'rake install' and then 'bundle install' in my Rails app, then bundler seems to think the gem has not been 'touched' (since no version change?) and hence my Rails app uses the old "cached" gem (NoMethodError). Would be nice with a new bundler task, which forces a certain gem (gems or all gems!) to be resolved anew. $ bundler update GEM $ bundler update devise-assistant $ bundler update gem1 gem2 gem3 $ bundler update-all or maybe $ bundler install --force-update devise-assistant Right now I have two options. Either do the version bump on the gem, then 'bundle install' or ... remove from Gemfile, run 'bundle install' reinsert in gemfile, run 'bundle install'. Yikes! Maybe I should make a batch script or thor task to facilitate this hack :P haha! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
