Array#split preserving the calling array

Remove @order attribute from collector

Ruby 1.8 legacy. Since 1.9 hash preserves insertion order. No need for additional array to achieve this

Improve Errors when Controller Name or Action isn't specfied

Add test for ActiveRecord::Relation YAML serialization, for #5303 issue

Update tzinfo

Include the tzinfo-data in the generated Gemfile on Windows.

instead of 'rake test' as shortcut, use 'rake'.

Closes #12780 [ci skip]

This is the only argument that changes over the method calls so it is
better to it be the first one

clarified missleading message

(No database connection) sounds not be
able to connect database.

see more #12804

The generators entry point file is rails/generators so we need to make
sure uers will be able to use the generators when requiring that file.

Fixes #12802

This is a follow up to: 97f0d9a0
This change is also related to: df0edafa

This will make the conditional and to code clear

fix simple_format escapes own output when sanitize is set to true

The log output used to be confusing in situation where type casting has
"unexpected" effects. For example when finding records with a `String`.

BEFORE:

irb(main):002:0> Event.find("im-no-integer")
D, [2013-11-09T11:10:28.998857 #1706] DEBUG -- :   Event Load (4.5ms)  SELECT "events".* FROM "events" WHERE "events"."id" = $1 LIMIT 1  [["id", "im-no-integer"]]

AFTER:

irb(main):002:0> Event.find("im-no-integer")
D, [2013-11-09T11:10:28.998857 #1706] DEBUG -- :   Event Load (4.5ms)  SELECT "events".* FROM "events" WHERE "events"."id" = $1 LIMIT 1  [["id", 0]]

Skip test which is broken on jruby

Extract common code from number helpers to new delegator method.

This test is broken from quite a while & is expected to remain broken as
encoding issues are hardest to fix in JRuby. so lets skip this test for
now

fix broken url/formatting in Asset pipeline guide [ci skip]

Start Running tests on Stable JRuby

Fixes for LOT of bugs have now landed in Jruby 1.7.6, thus we no longer
need to run tests against the master.

for broken tests that are still remaning:
1. If problem is in rails - we fix that test/code
2. if its a JRuby bug - we skip that test & file a bug report for jruby.

This will avoid the broken window effect in our test suite

We can conditional define the tests depending on the adapter or
connection.

Lets keep the skip for fail tests that need to be fixed.

Update workaround for "Outside the Scope of Strong Parameters"