Piotr Sarnacki 35a1744a45 Allow to run migrations with given scope, with SCOPE=<scope> ... Scope in migrations can be defined by adding suffix in filename, like: 01_a_migration.blog.rb. Such migration have blog scope. Scope is automatically added while copying migrations from engine, so if you want to revert all of the migrations from given engine, you can just run db:migrate with SCOPE, like: rake db:migrate SCOPE=blog		2011-12-09 22:00:51 +01:00
..
application	Allow to run migrations with given scope, with SCOPE=<scope>	2011-12-09 22:00:51 +01:00
fixtures	treat USAGE as an ERB template	2011-11-02 09:00:18 -04:00
generators	Simplifying test in app/generator	2011-12-03 16:12:02 +05:30
isolation	rake assets:precompile loads the application but does not initialize it.	2011-09-24 03:17:23 +02:00
railties	Add suffix for migrations copied from engines	2011-12-09 11:45:19 +01:00
abstract_unit.rb	Use RAILS_ISOLATED_ENGINE and fix namespaced generators tests	2011-06-07 12:16:05 +02:00
backtrace_cleaner_test.rb	Use backtrace cleaner for dev mode exception page	2010-01-16 21:34:35 -06:00
generators_test.rb	treat USAGE as an ERB template	2011-11-02 09:00:18 -04:00
initializable_test.rb	:group => :assets should only run in the assets environment.	2011-10-02 22:08:33 +02:00
paths_test.rb	Removing Deprecated Path API tests	2011-05-24 23:03:01 -05:00
rails_info_controller_test.rb	Loading action_controller twice removed.	2011-05-22 02:14:17 +05:30
rails_info_test.rb	Takes out stale methods relating to edge_rails_version	2010-05-16 17:21:29 +02:00
script_rails_loader_test.rb	Deletes trailing whitespaces (over text files only find * -type f -exec sed 's/[ \t]*$//' -i {} \;)	2010-08-14 04:12:33 -03:00