…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 <email@example.com>
… files from test directly. [#1135 state:resolved]
…evious versions. Signed-off-by: Michael Koziarski <firstname.lastname@example.org>
…el command Signed-off-by: Joshua Peek <email@example.com>
* 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 <firstname.lastname@example.org>
…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 <email@example.com>
…block parameters [#1000 state:resolved] Signed-off-by: Jeremy Kemper <firstname.lastname@example.org>
[#1001 state:resolved] Signed-off-by: Jeremy Kemper <email@example.com>
[#1002 state:resolved] Signed-off-by: Jeremy Kemper <firstname.lastname@example.org>
…on call. Pools start out empty and grow as necessary to a maximum size (default is 5, configure size with key 'pool' in your database configuration). If no connections are available, a thread will wait up to a 'wait_timeout' time (default is 5 seconds). Connections are verified and reset when checked out from the pool (usually upon first access to ActiveRecord::Base.connection), and returned back to the pool after each request. If you would like to use connection pools outside of ActionPack, there is an ActiveRecord::Base.connection_pool method that gives you access to the pool, and you can manually checkout/checkin connections, or supply a block to ActiveRecord::Base.connection_pool.with_connection which takes care of the checkout/checkin for you. [#936 state:resolved]
…by 1.9, but it has since been removed from 1.9. Signed-off-by: Jeremy Kemper <email@example.com> Conflicts: actionpack/test/controller/layout_test.rb
[#939 state:resolved] Signed-off-by: Jeremy Kemper <firstname.lastname@example.org>
…gexes." This reverts commit 3d2512d38d2e28b3ea669139f7c7b0307522aa72.
This is more friendly to JRuby/JDBC adapters (with names like 'jdbcmysql') and leaves the door open to alternate implementations of adapters in the future.