…d the corresponding test suites to be cleaner. [#5434 state:resolved] Signed-off-by: José Valim <email@example.com>
…cts the current app name whenever possible. This means that renaming the residing directory will not effect the app name generated by AppGenerator. [#5225 state:resolved] Signed-off-by: José Valim <firstname.lastname@example.org>
[#5245 state:committed] Signed-off-by: Santiago Pastorino <email@example.com>
…ed to --skip-test-unit and --skip-active-record respectively Reason is their proper spellings are "Test::Unit" and "Active Record". Option names and descriptions have been revised, as well as some method names and minor details here and there.
Signed-off-by: David Heinemeier Hansson <firstname.lastname@example.org>
Also removed the limitation of not being able to call your new server any of the rails commands (generate, server, dbconsole, console etc) as there is no longer any ambiguity here. http://rails.lighthouseapp.com/projects/8994/tickets/4665 Signed-off-by: David Heinemeier Hansson <email@example.com>
Signed-off-by: José Valim <firstname.lastname@example.org>
…ator [#4602 state:resolved] Signed-off-by: José Valim <email@example.com>
…hat handles the individual elements of generating a new Rails application
…rride targeted areas
…lesheet." This reverts commit ea2c5fa. Conflicts: railties/lib/rails/generators/rails/app/templates/app/views/layouts/application.html.erb railties/test/generators/app_generator_test.rb
NOTE: This does not fix the bundler activation issue. The "bundler" gem will still be installed and activated when you install rails.
…ing the former since it's less obstrusive.
…spec:install generator, you need generators/rspec/install_generator in your load path.