There has been many complaints about Bundler, requires and gem require ordering issues. I know that Bundler does now or will support requiring all the gems in the order specified in the Gemfile but still there was an issue with Merb requiring bundler for it's work.
I did some patches some time ago and I'm testing that on my apps to remove this dependencies and implicit requiring of the gems using Bundler.require. Current code is in the merb/master as 1.2. Please for more explanation read http://wiki.github.com/merb/merb/release-120 So what I did and how it influence current apps? I've removed bundler dependency and bundler calls from the Bootladers. This means a) You don't need to use Bundler with merb b) At some point YOU need to require your gems Many people like to require gems in the runtime at the point when they need the gem and not to require all gems during the booting. Basically what you need to do with your app on 1.2 is add either Bundler.require (if bundler requires gems in correct order) to your init.rb or add explicit requires (recommended) to init.rb or separate file which is required in the init.rb. New generated applications now generate init with explicit requires. Feedback welcome! Pavel -- You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en.
