mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
ad0f0e6980
This almost never matters, but if the path-global 'rake' or 'rails' points to a specific (and wrong) ruby version, (or, possible in CI, there is no installed 'rails' executable), things get confused. Instead, any time we mean "run a global 'rails', as for 'new'", use a fully-qualified path to our in-tree copy. And any time we're working inside an application, use the bin/rails script directly. It would be equivalently valid to always use the one in exe/, because that handles searching for bin/rails internally... but it's uglier to fully-qualify, plus 'rake' would then be more complicated. |
||
|---|---|---|
| .. | ||
| application | ||
| command | ||
| commands | ||
| configuration | ||
| engine | ||
| fixtures | ||
| generators | ||
| isolation | ||
| minitest | ||
| railties | ||
| test_unit | ||
| abstract_unit.rb | ||
| app_loader_test.rb | ||
| backtrace_cleaner_test.rb | ||
| code_statistics_calculator_test.rb | ||
| code_statistics_test.rb | ||
| console_helpers.rb | ||
| engine_test.rb | ||
| env_helpers.rb | ||
| generators_test.rb | ||
| initializable_test.rb | ||
| json_params_parsing_test.rb | ||
| path_generation_test.rb | ||
| paths_test.rb | ||
| rack_logger_test.rb | ||
| rails_info_controller_test.rb | ||
| rails_info_test.rb | ||
| secrets_test.rb | ||
| version_test.rb | ||