Fixes bug where merb-gen wasn't able to generate any apps anymore. Tries to load the dependencies like this: 1. Use Merb::Config[:gemfile] or default Gemfile 2a. Try to require an already bundled environment 2b. If a Gemfile is present, use bundler to load it 2c. Warn if no Gemfile can be found
Merb rely on Rack for parameter encoding. ENV from Rack is in ASCII by default. It is possible to cast the whole Rack ENV to UTF-8 but there is problem with Merb::Parse#unescape which turns UTF-8 strings back to the ASCII. This patch allows to pass encoding to the Merb::Parse#unescape to force encoding. This is only possible on Ruby 1.9. When on Ruby 1.9. and encoding parameter is not passed unescape defaults to the Encoding.default_internal which is nil by default. If all attempts to get non-nil value fails no force encoding is called and all strings are untouched. So for uscase where you want your application to work in UTF-8 exclusively you can set Encoding.default_internal = 'UTF-8' and all your parameters will be in UTF-8.
To use this feature you need to have disable_rubygems in your Gemfile. And if you want you can use also disable_system_gems. For Ruby >= 1.9 you must change your ./bin/merb file and use shebang #!/path/to/your/ruby1.9.1 --disable-gems -S Now you can run your Merb application without system and RubyGems loaded in the runtime.
Method start_with? is not included in the 1.8.6.
Please refer to CHANGELOG and http://wiki.github.com/merb/merb/howto-using-the-bundler
Adding default charset attribute to the js_include_tag in the same way as css_include_tag works right now. So default charset is utf-8 and is it possible to override it using :charset => 'xy' option. Fixing specs to pass on 1.9.1. The issue would probably be valid for other versions and implementations as well. Since it involves order how attributes are ordered inside the script tag. I think we should check for the attribute existence and value not the order.
This merb-gen patch provides newly generated apps with the ability to work seamlessly with the bundler, whether you run merb, rake, spec from either your local system gem path or from bin/merb, bin/rake, bin/spec. No more having to bundle rake and rspec. w00t!
Having DM_VERSION and DO_VERSION constants in merb-core feels wrong. The simplest solution for now is to duplicate the DM_VERSION_REQUIREMENT (already defined in merb_datamapper) in order to be able to write out a proper merb stack Gemfile.