Resolution of https://github.com/bundler/bundler/issues/1041

[Vinay Vasudevamurthy]

Curious to know what is the resolution of this issue. The comments were really long and I could not make out what the resolution was.

I have a similar problem and posted a question on here
http://stackoverflow.com/questions/24842080/need-to-require-gem-in-the-application-even-though-gemspec-adds-it-as-a-runtime?noredirect=1#comment38572238_24842080

[André Arko]

The answer is in your stack overflow question: that is how gems work. Gems don’t get to use Bundler.require, so you _must_ add `require ‘dependency_name’` statements to your gem itself for every dependency.

> --
> You received this message because you are subscribed to the Google Groups "ruby-bundler" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ruby-bundler...@googlegroups.com.
> To post to this group, send email to ruby-b...@googlegroups.com.
> Visit this group at http://groups.google.com/group/ruby-bundler.
> For more options, visit https://groups.google.com/d/optout.