diff options
| author | Piotr Sarnacki <drogus@gmail.com> | 2012-05-16 04:46:26 -0700 |
|---|---|---|
| committer | Piotr Sarnacki <drogus@gmail.com> | 2012-08-31 20:52:29 +0200 |
| commit | 62fa173bd9117cf2bc93c01984b8decfcc78accb (patch) | |
| tree | 5cd4ebb8c3e27a9d8266fd9b1769b27a0e7d6939 /activerecord/test/cases/autosave_association_test.rb | |
| parent | 7fc4b4681b83b86d5871f0726460ea808bd76f1b (diff) | |
| download | rails-62fa173bd9117cf2bc93c01984b8decfcc78accb.tar.gz rails-62fa173bd9117cf2bc93c01984b8decfcc78accb.tar.bz2 rails-62fa173bd9117cf2bc93c01984b8decfcc78accb.zip | |
Don't use Gemfile in test application in railties
Option to run `bundle install` after generating new appplication was
added recently to rails. Since introduction, it contained a subtle bug
that caused it to use `Gemfile` from current directory (if it exists)
rather than from generated directory. This also accidentaly caused
railties tests to work without any problems - after generating test app
it just used `Gemfile` from the repository, rather than the one in
generated app. After fixing the bug mentioned above, this of course
broke. The easiest way to bypass that is to not generate a `Gemfile` for
test application - with such setup Bundler will just use first available
`Gemfile` in one of the parent directories.
Diffstat (limited to 'activerecord/test/cases/autosave_association_test.rb')
0 files changed, 0 insertions, 0 deletions