> > Not sure I understand why. > Quite simple: you have always to leave your app in a good working state if you want to successfully run generators or plugin installation (that rely on the app environment).
If you have a reference to some method that is defined in a gem, you application will not start (i.e. the environment will not load) unless the gem is loaded by the gemfile. If you remove the gem you have to remove the references to that gems BEFORE the `rails plugin install...` command, OR just leave the application in its current working state (i.e. don't change a thing) and install the plugin. After the installation you can remove the gem call because the plugin will define the method in its place. ciao dd On Tue, Apr 19, 2011 at 1:58 PM, Tim Griffin <[email protected]> wrote: > Wait a sec. That didn't make any sense. > > I just found that I had to leave my original reference to acts_as_list in > my Gemfile, do the plugin install, and then remove it from my Gemfile. The > reference to acts_as_list had to be in the Gemfile in order for the plugin > install process not to choke on the reference in my model. > > Now I have the plugin installed, I can remove the reference in my Gemfile. > > Not sure I understand why. > > T > > -- > You received this message because you are subscribed to the Google Groups > "Hobo Users" 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/hobousers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
