Piotr Sarnacki 1395545404 Do not run migrations from mounted engine separately. ... 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: José Valim <jose.valim@gmail.com>		2010-11-16 22:58:13 +01:00
..
erb	Change inside_namespace method to inside_template and use it in all templates by default	2010-11-16 16:38:14 +01:00
rails	Do not run migrations from mounted engine separately.	2010-11-16 22:58:13 +01:00
test_unit	Fix scaffold generator to be aware of namespace in isolated engine	2010-11-03 20:48:40 +01:00
actions.rb	Fixing two minor errors in Rails::Generators::Actions initializer method comments	2010-10-08 19:19:17 -02:00
active_model.rb
app_base.rb	Properly skip test unit in 'plugin new' generator	2010-11-02 17:14:53 +01:00
base.rb
erb.rb
generated_attribute.rb
migration.rb	Remove existing migration when using 'rails generate model' with --force [#5526 state:committed]	2010-09-18 21:22:29 +02:00
named_base.rb	Change inside_namespace method to inside_template and use it in all templates by default	2010-11-16 16:38:14 +01:00
resource_helpers.rb	Merge remote branch 'drogus/plugin_new'	2010-11-11 19:39:21 +01:00
test_case.rb
test_unit.rb