There is no good way now to run migrations for mounted engine in test application,
but that way of running migrations makes it really hard to run
engine in development mode and test it (you need to copy migrations
in dev mode and in that case in tests they will be run twice).
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

The initial implementation of namespacing was based on wrong
assumptions. Namespacing path and class names in templates
should be based on current namespace and skip_namespace attribute,
but it should be not necessary to wrap content on all the templates
into additional block methods.

[#5978 state:committed]

adds a publish_docs task to force stable docs generation and publishing after a new stable tag has been pushed

Brought the domain method in AD http url inline with subdomain where @@tld_length is used by default. Also set the default value of @@tld_length to 1.

updated the rails guide to reflect changes in the action view railtie relating to the asset id cache code

changed asset_timestamps_cache to asset_ids_cache, added an rdoc comment to the new public api, and updated the railtie

corrected the AV railtie to use the new home for cache_asset_timestamps, and merged asset id caching and asset paths together.

reorganised the the common asset helpers module into a class and have it include the id caching module, this class is now shared from the view instance to the asset include tag helpers (js and css)

reduced duplication between the javascript and stylesheet asset tag methods, also split the asset id caching methods into a separate module for easy inclusion and use by the asset include tag class and base asset tag helpers

separated the asset id methods to a separate module, removed some dupliation with the various path methods, and moved the base asset tag methods to a base module so the asset id module can play nice with the path generation

split the javascript and stylesheet tag helpers into separate files as a precusor before removing the duplication between the two

  rails new APP_PATH [options]

Options:
  -G, [--skip-git]            # Skip Git ignores and keeps
  -r, [--ruby=PATH]           # Path to the Ruby binary of your choice
                              # Default: /Users/drogus/.rvm/rubies/ruby-1.8.7-p302/bin/ruby
  -b, [--builder=BUILDER]     # Path to an application builder (can be a filesystem path or URL)
      [--edge]                # Setup the application with Gemfile pointing to Rails repository
      [--dev]                 # Setup the application with Gemfile pointing to your Rails checkout
      [--skip-gemfile]        # Don't create a Gemfile
  -d, [--database=DATABASE]   # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db)
                              # Default: sqlite3
  -O, [--skip-active-record]  # Skip Active Record files
  -m, [--template=TEMPLATE]   # Path to an application template (can be a filesystem path or URL)
  -J, [--skip-prototype]      # Skip Prototype files
  -T, [--skip-test-unit]      # Skip Test::Unit files

Runtime options:
  -s, [--skip]     # Skip files that already exist
  -p, [--pretend]  # Run but do not make any changes
  -f, [--force]    # Overwrite files that already exist
  -q, [--quiet]    # Supress status output

Rails options:
  -v, [--version]  # Show Rails version number and quit
  -h, [--help]     # Show this help message and quit

Description:
    The 'rails new' command creates a new Rails application with a default
    directory structure and configuration at the path you specify.

Example:
    rails new ~/Code/Ruby/weblog

    This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
    See the README in the newly created application to get going. command

if association is already loaded and if a find operation is performed on the already loaded association list with an empty hash then do not perform another sql

[#5972 state:resolved]