[#1326 state:committed] Signed-off-by: Jeremy Kemper <firstname.lastname@example.org>
Signed-off-by: David Heinemeier Hansson <email@example.com>
…ng of all locales in config/locales/*.rb,yml, and config/locales/en.yml as a sample locale [DHH]
…p" -- it broke all the tests! This reverts commit 9a88ab6.
…ch path. Use Gem.clear_paths to ensure we get a current searcher. Signed-off-by: Michael Koziarski <firstname.lastname@example.org>
…tiveSupport::TestCase, also introduced a helper script to reduce the needed require statements. [#1137 state:committed] Signed-off-by: David Heinemeier Hansson <email@example.com>
…rails application : rake doc:guides The rake task will generate guides inside doc/guides directory of your application. Open index.html to browse.
…nd silence spec warnings on refresh. [#1128] Signed-off-by: Pratik Naik <firstname.lastname@example.org>
… files from test directly. [#1135 state:resolved]
…evious versions. Signed-off-by: Michael Koziarski <email@example.com>
…el command Signed-off-by: Joshua Peek <firstname.lastname@example.org>
* Rails::GemDependency was missing definitions for hash and eql?, causing Array#uniq to not work. * If several versions of a gem are unpacked in vendor, now chooses the highest if no version is specified. * streamlined add_load_path. Now sets up Rubygems correctly to allow 'gem' to find frozen gems, with gems frozen to vendor/gems and specifications in vendor/gems/<gem-name>/.specification * Rails::GemDependency#specification would return a spec for the highest installed version, even for frozen gems and/or previously loaded lower versions. See in part ticket #1123. * removed vendor from default_load_paths - it was causing autoloading to append Gems::Gems::<gem-dir> to constant names * added additional tests for loading frozen gems. * incorporates the fix from #1107 for vendor rails * defers to freeze:gems for handling the Rails framework. gems:unpack WILL NOT place a copy of Rails in vendor/gems. Should close #1123 completely. * incorporates, via using the gem loader for frozen gems, fixes corresponding to #227, #324, #362, #527, and #742. * gem plugins now work the same whether frozen or not. Correctness of the behavior is a matter for another ticket... Signed-off-by: rick <email@example.com>
…an the previous release. This allows people tracking non-release gems or git submodules to use the constants.
…hat specific migration to redo Signed-off-by: Michael Koziarski <firstname.lastname@example.org>