aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib
Commit message (Collapse)AuthorAgeFilesLines
* Rakefiles are executables, and rake loads rake, not rakefile coderaggi2010-11-253-5/+3
|
* Update to Prototype 1.7Santiago Pastorino2010-11-231-326/+407
| | | | [#6042 state:committed]
* Ensure that app generator is not loaded twice to get rid of warningsPiotr Sarnacki2010-11-221-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Do not create table_name_prefix method on isolated module if the method ↵Piotr Sarnacki2010-11-221-2/+4
| | | | | | already exists. Signed-off-by: José Valim <jose.valim@gmail.com>
* Minor fix on Rails:Railtie documentationzhengjia2010-11-211-2/+2
|
* do not require ruby-debug automatically. please require it if you have ↵Aaron Patterson2010-11-191-11/+0
| | | | declared it as a dependency
* Tidy up generators commits.José Valim2010-11-172-4/+2
|
* Update the version.rb files to include a PRE partCarl Lerche2010-11-161-2/+2
|
* Do not run migrations from mounted engine separately.Piotr Sarnacki2010-11-161-2/+0
| | | | | | | | | 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>
* Fix plugin new --mountable: ActionController instead of ActiveControllerPiotr Sarnacki2010-11-161-1/+1
|
* Change inside_namespace method to inside_template and use it in all ↵Piotr Sarnacki2010-11-166-31/+20
| | | | | | | | | | templates by default 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.
* Fix misspelling of 'deprecation' in plugin_generator.Doug Ireton2010-11-161-1/+1
|
* Do not allow to use plugin_new generator directly, you should use Usage:Piotr Sarnacki2010-11-161-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Allow running `rails plugin new` command inside rails applicationPiotr Sarnacki2010-11-161-6/+11
|
* Bye bye bang bang.Piotr Sarnacki2010-11-161-1/+1
|
* There is no need to make isolated? method with bang-bang, just alias isolatedPiotr Sarnacki2010-11-161-4/+1
|
* Deprecate plugin generatorPiotr Sarnacki2010-11-161-0/+7
|
* Add skip-gemspec option to 'plugin new' generatorPiotr Sarnacki2010-11-161-7/+10
|
* Don't need to support rails plugin --versionPiotr Sarnacki2010-11-161-6/+0
|
* Update to JQuery 1.4.4Santiago Pastorino2010-11-121-344/+640
| | | | | Check out http://blog.jquery.com/2010/11/11/jquery-1-4-4-release-notes/ for information on what's new.
* Merge remote branch 'drogus/plugin_new'José Valim2010-11-1138-152/+665
|\ | | | | | | | | Conflicts: railties/test/generators/app_generator_test.rb
| * Allow to set dummy application path through optionsPiotr Sarnacki2010-11-081-1/+4
| |
| * Fix scaffold generator to be aware of namespace in isolated enginePiotr Sarnacki2010-11-0310-5/+25
| |
| * Add --mountable option to 'plugin new' generator which generates full ↵Piotr Sarnacki2010-11-026-3/+43
| | | | | | | | mountable application (engine)
| * Add example rake task to 'plugin new' generatorPiotr Sarnacki2010-11-022-0/+5
| |
| * create_dummy_app method that allows to easily create dummy application from ↵Piotr Sarnacki2010-11-023-37/+32
| | | | | | | | template
| * Properly skip test unit in 'plugin new' generatorPiotr Sarnacki2010-11-024-21/+17
| |
| * Properly handle other databases in 'plugin new' generatorPiotr Sarnacki2010-11-024-22/+29
| |
| * Skip active record properly in 'plugin new' generatorPiotr Sarnacki2010-11-021-1/+1
| |
| * Use rails integration tests by default in 'plugin new' generatorPiotr Sarnacki2010-11-025-15/+7
| |
| * We don't need to configure ActionMailer in plugin's test helper, it's ↵Piotr Sarnacki2010-11-021-4/+0
| | | | | | | | configured by dummy app
| * Refactor app and plugin generators to use new Thor APIPiotr Sarnacki2010-11-022-20/+4
| |
| * Make deep copy of application generators on engine initialization.Piotr Sarnacki2010-11-022-1/+9
| | | | | | | | | | Otherwise nested hashes will be same objects for both application and engine, which will result in overwriting each others values on changes.
| * Use application's generators defaults as engine defaults to not force users ↵Piotr Sarnacki2010-11-021-0/+1
| | | | | | | | to manually set it
| * Do not create additional newlinePiotr Sarnacki2010-11-021-1/+1
| |
| * Don't be verbose while creating dummy application in plugin new generatorPiotr Sarnacki2010-11-021-3/+13
| |
| * No need to require 'app_base', it's required in app_generatorPiotr Sarnacki2010-11-021-1/+0
| |
| * Pass more options to test/dummy in 'plugin new' generatorPiotr Sarnacki2010-11-023-16/+14
| |
| * Add --full option to 'plugin new' generator, which generates rails enginePiotr Sarnacki2010-11-0212-8/+78
| |
| * No need for say_step in 'plugin new' generatorPiotr Sarnacki2010-11-022-18/+1
| |
| * DRY up app generator and plugin new generator. Moved shared options to ↵Piotr Sarnacki2010-11-023-52/+31
| | | | | | | | AppBase generator
| * Remove integration tests and ActionModel/ActiveRecord calls from 'rake ↵Piotr Sarnacki2010-11-026-35/+5
| | | | | | | | plugin new' generator, it shouldn't be available as default option
| * We don't need gem tasks, we have a gemspecPiotr Sarnacki2010-11-021-17/+0
| |
| * Builder should not be responsible for running store_application_definition ↵Piotr Sarnacki2010-11-021-1/+1
| | | | | | | | method
| * Make tests for app and plugin generators more DRYPiotr Sarnacki2010-11-021-1/+1
| |
| * Allow easy overriding of test framework in 'rake plugin new' generator, ↵Piotr Sarnacki2010-11-023-16/+32
| | | | | | | | using PluginBuilder
| * Add --dev and --edge options to rails plugin newPiotr Sarnacki2010-11-025-25/+48
| |
| * Added USAGE for rails plugin newPiotr Sarnacki2010-11-021-0/+10
| |
| * That method is already declared at AppBasePiotr Sarnacki2010-11-021-23/+0
| |
| * Add support for templates for rails plugin newPiotr Sarnacki2010-11-023-15/+30
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 08:47:34 +0000