aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/generators/plugin_new_generator_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* change sqlite3-ruby => sqlite3 in the generatorsAaron Patterson2011-01-161-1/+1
|
* README.rdoc is a templateSantiago Pastorino2011-01-151-0/+1
|
* plugin new generator should generate config/routes.rb file for full enginesSantiago Pastorino2011-01-141-1/+3
|
* Generate default layout in engine with --mountable optionPiotr Sarnacki2010-12-161-0/+1
|
* Generate javascripts in engine with --mountable optionPiotr Sarnacki2010-12-161-0/+29
|
* Rake tasks for managing database while development and testing of enginesPiotr Sarnacki2010-12-091-1/+1
| | | | | | | | | | | | Some of the engines needs database. As engine needs to be run inside Rails application, migrations and other database operations are run from dummy application. To make that process simple I changed db tasks to look for migrations in both engine's and application's db/migrate directory. You can run all of the database tasks from test/dummy or directly from engine with prefix app, like: rake app:db:migrate rake app:db:migrate:redo
* Fix plugin new --mountable: ActionController instead of ActiveControllerPiotr Sarnacki2010-11-161-1/+1
|
* Add skip-gemspec option to 'plugin new' generatorPiotr Sarnacki2010-11-161-0/+5
|
* Remove whitespaces and add missing test.José Valim2010-11-111-1/+0
|
* Allow to set dummy application path through optionsPiotr Sarnacki2010-11-081-0/+7
|
* Add --mountable option to 'plugin new' generator which generates full ↵Piotr Sarnacki2010-11-021-0/+9
| | | | mountable application (engine)
* Add example rake task to 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+1
|
* create_dummy_app method that allows to easily create dummy application from ↵Piotr Sarnacki2010-11-021-1/+8
| | | | template
* Properly handle other databases in 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+17
|
* Skip active record properly in 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+1
|
* Use rails integration tests by default in 'plugin new' generatorPiotr Sarnacki2010-11-021-3/+1
|
* Don't be verbose while creating dummy application in plugin new generatorPiotr Sarnacki2010-11-021-0/+4
|
* Pass more options to test/dummy in 'plugin new' generatorPiotr Sarnacki2010-11-021-0/+15
|
* Add --full option to 'plugin new' generator, which generates rails enginePiotr Sarnacki2010-11-021-1/+27
|
* No need for say_step in 'plugin new' generatorPiotr Sarnacki2010-11-021-4/+3
|
* Remove integration tests and ActionModel/ActiveRecord calls from 'rake ↵Piotr Sarnacki2010-11-021-7/+1
| | | | plugin new' generator, it shouldn't be available as default option
* Make tests for app and plugin generators more DRYPiotr Sarnacki2010-11-021-137/+16
|
* Allow easy overriding of test framework in 'rake plugin new' generator, ↵Piotr Sarnacki2010-11-021-0/+10
| | | | using PluginBuilder
* Ensure that tests run properlyPiotr Sarnacki2010-11-021-0/+7
|
* Change // style regexp to %r{}, to not confuse editors code highlightingPiotr Sarnacki2010-11-021-1/+1
|
* Add --dev and --edge options to rails plugin newPiotr Sarnacki2010-11-021-0/+13
|
* Add support for templates for rails plugin newPiotr Sarnacki2010-11-021-0/+20
|
* Ensure that options for plugin new generator are not passed to application ↵Piotr Sarnacki2010-11-021-0/+6
| | | | generator
* Added 'rails plugin new' generator which generates gem plugin skeleton.Piotr Sarnacki2010-11-021-0/+179
This command is based on enginex gem by José Valim. It generates gem structure and ads dummy application into test/dummy. This can be used to start developing any kind of extension for rails 3.