Run `rake bundle` before running tests.

The use of encryption prevents people from seeing any potentially secret values you've used.  It also supports and encrypt_and_sign model to prevent people from tampering with the bits and creating random junk that gets fed to

A motivated coder could use this to add an :encrypt=>true option to the cookie store.

Add config.preload_frameworks to load all frameworks at startup. Default to false so Rails autoloads itself as it's used.

Autoload ActiveSupport::Duration, Gzip, OptionMerger, OrderedHash, OrderedOptions, StringInquirer, TimeWithZone, and TimeZone also

Add ActiveSupport::MessageVerifier to aid users who need to store tamper-proof messages in cookies etc.

This is particularly useful for things like remember-me tokens in web applications and auto-unsubscribe links in emails.

Added ActiveSupport::BacktraceCleaner and Rails::BacktraceCleaner for cutting down on backtrace noise (inspired by the Thoughtbot Quiet Backtrace plugin) [DHH]

Signed-off-by: NDavid Heinemeier Hansson <david@loudthinking.com>

I18n: Introduce I18n.load_path in favor of I18n.load_translations and change Simple backend to load translations lazily. [#1048 state:resolved]
Signed-off-by: NPratik Naik <pratiknaik@gmail.com>

SecureRandom has a few minor security enhancements and can be used as a drop-in replacement
Signed-off-by: NMichael Koziarski <michael@koziarski.com>
[#913 state:committed]

Harmonize framework require strategy. Don't add self to load path since Rails initializer and RubyGems handle it.