I had failed to require the Gem's dependencies in the Gem's init (my_gem_name.rb) lib file. A simple require 'authlogic' did it.
Elliott G On Sep 20, 2:56 pm, elliottg <[email protected]> wrote: > I am working on a Gem that has several Gem dependencies of its own. > The Gem's .gemspec looks good (I think) and when "bundle install" is > called from the parent app, it lists that it is indeed "Using" the > Gem's required Gems. I'll refrain from an Inception analogy here ;) > > When I fire up the app and make a request, I get "uninitialized > constant Authlogic" (this is one of the Gem's dependencies). If I add > "gem 'authlogic'" to the app's Gemfile all is good. > > I was under the impression that a Gem's dependencies did not need to > be added to the parent app's Gemfile. Am I wrong here? Do I need to > configure something differently in my Gem so that the explicit Gemfile > calls are not needed? > > Thanks, Elliott G -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
