summaryrefslogtreecommitdiff
path: root/lib/bundler/cli.rb
Commit message (Collapse)AuthorAgeFilesLines
* Typo. s/expect/except/David Rodríguez2019-04-051-1/+1
|
* Remove `list_command` settingDavid Rodríguez2019-04-051-15/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The list command was still present (just aliased to `bundle show`), even if the setting was set to false. So the setting was at least super confusing if not just wrong. It also led to misleading situations such as ``` $ bundle list --help (...) NAME bundle-list - List all the gems in the bundle SYNOPSIS bundle list [--name-only] [--paths] [--without-group=GROUP] [--only-group=GROUP] (...) $ bundle list --only-group=development Unknown switches '--only-group=development' ``` So, instead, I enable the new list command _always_ and remove the `bundle list => bundle show` alias.
* Print a better messages on undocumented flagsDavid Rodríguez2019-04-051-8/+12
| | | | | Inform about complete removal when `bundle show --outdated` and `bundle show --verbose`.
* Remove `bundle show` from bundler 3David Rodríguez2019-04-051-27/+28
|
* Remove `console_command` settingremove_command_removal_settingsDavid Rodríguez2019-03-311-1/+1
| | | | | | | | This setting is not meant to be used by end users. The `console` command is going away and we plan to fully remove the code once we only have to maintain bundler 3 or higher versions. Adding a setting makes it look like the presence of this command is something "configurable", but it's not.
* Remove `viz_command` settingDavid Rodríguez2019-03-311-1/+1
| | | | | | | | This setting is not meant to be used by end users. The `viz` command is going away and we plan to fully remove the code once we only have to maintain bundler 3 or higher versions. Adding a setting makes it look like the presence of this command is something "configurable", but it's not.
* Allow `update` to install when `--no-install` usedno_install_allows_update_to_installDavid Rodríguez2019-03-281-1/+3
| | | | The `--no-install` flag flag is only meant for `bundle package`.
* Move message to present tenseDavid Rodríguez2019-03-171-1/+1
| | | | Because the behavior is still there.
* The cops got meDavid Rodríguez2019-03-121-1/+1
|
* Deprecate a bunch of flags in bundler 2David Rodríguez2019-03-121-17/+34
| | | | | | | Under the previous code, once we stop remembering options, these flags would be automatically removed without deprecation. Instead, first deprecate the options in bundler 2, then remove them and stop remembering them in bundler 3.
* Move `rescue Exception` exceptions inlineDavid Rodríguez2019-03-041-1/+1
|
* Use newest interface to `bundle config` everywhereDavid Rodríguez2019-02-191-4/+4
|
* Enable gemfile flag for bundle lockLaura Paakkinen2018-10-181-0/+2
|
* Refactor initial codecorrect_bundle_show_deprecationDavid Rodríguez2018-10-011-7/+5
|
* Fix `--paths` argument handlingDavid Rodríguez2018-10-011-1/+9
|
* Fix "bundle show" deprecation messagesDavid Rodríguez2018-10-011-1/+9
| | | | | With a single gem, it will be replaced by `bundle info`, not by `bundle list`.
* Make the equivalent change to `bundle update`David Rodríguez2018-09-181-1/+2
|
* Fix issue with initial implementationDavid Rodríguez2018-09-181-1/+1
|
* Deprecate `bundle install --force`David Rodríguez2018-09-181-2/+2
| | | | | | | | | | | | | | | | Instead of hard erroring, deprecate the `--force` flag on bundler 2 to better teach users about the replacement. Before: $ bundle install --force Unknown switches '--force' After: $ bundle install --force [DEPRECATED FOR 2.0] The `--force` option has been renamed to `--redownload` Could not locate Gemfile # or whatever the expected behavior for --redownload is
* Add gemfile flag to exec commandankitkataria2018-08-241-0/+1
|
* Update documentationAgrim Mittal2018-07-011-2/+2
|
* Remove necessary comments and update documentationAgrim Mittal2018-06-281-2/+2
|
* Remove necessary comments and update docsAgrim Mittal2018-06-281-2/+2
|
* Add gemfile error when gem is not presentAgrim Mittal2018-06-281-3/+3
|
* Update documentationAgrim Mittal2018-06-281-2/+2
|
* Add install flag to removeAgrim Mittal2018-06-281-1/+3
|
* Add support for mutiple gems and add failing specsAgrim Mittal2018-06-281-4/+4
|
* Add remove function to cliAgrim Mittal2018-06-281-0/+9
|
* Change options to --without-group and --only-groupAgrim Mittal2018-06-171-2/+2
| | | | Improves understanding of the options without need to look up the docs.
* abstract group separation logic based on optionsAgrim Mittal2018-06-151-2/+2
|
* add initial draft of without and only optionsAgrim Mittal2018-06-151-0/+2
|
* Auto merge of #6547 - agrim123:agr-add-mutiple-gems-names, r=segiddinsThe Bundler Bot2018-06-151-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | Add mutiple gems by names Add support for mutiple gems by names only ```bash bundle add rack rails ``` Concerns: - All the options/switches used would be applied to the all gems specified and a warning is displayed for the time being. Closes #6543
| * Add support for mutiple gems add with names onlyAgrim Mittal2018-06-061-2/+2
| |
* | Auto merge of #6531 - peret:outdated-filter-dependencies, r=segiddinsThe Bundler Bot2018-06-151-0/+2
|\ \ | |/ |/| | | | | | | Add option to filter gem-dependencies from output of 'bundle outdated' Resolves #5366 by adding a new option '--filter-dependencies' to `bundle outdated`. When present, `outdated` will only check the `gemfile_specs` and skip the `dependency_specs`.
| * Rename --filter-dependencies to --only-explicit.Peter Retzlaff2018-06-041-1/+1
| |
| * Add new option --filter-dependencies to 'bundler outdated'.Peter Retzlaff2018-05-111-0/+2
| | | | | | | | | | When enabled, 'bundler outdated' will only check gems specified in the Gemfile and ignore their transitive dependencies.
* | Add documentation for optionsAgrim Mittal2018-05-291-2/+2
| |
* | add version prefixAgrim Mittal2018-05-281-0/+2
| |
* | Add documentation for --skip-install flagAgrim Mittal2018-05-141-1/+1
| |
* | Add --skip-install flag to bundle addAgrim Mittal2018-05-021-1/+2
|/
* [Binstubs] Add --all optionssegiddins/bundle-binstubs-allSamuel Giddins2018-04-181-0/+2
|
* Fix some rescue calls that do not specifiy error type.utilum2018-03-171-1/+1
|
* Auto merge of #6273 - joelvh:feature/bundle_update_gemfile_option, ↵The Bundler Bot2018-01-311-0/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r=colby-swandale Added `--gemfile` option to `bundle update` Thanks so much for the contribution! To make reviewing this PR a bit easier, please fill out answers to the following questions. ### What was the end-user problem that led to this PR? The problem was that `BUNDLE_GEMFILE` is not respected when `.bundle/config` specifies an alternate Gemfile. However, my specific issue is that `bundle install --gemfile Gemfile2` is an option, but `bundle update` won't let me specify an alternate Gemfile. ### What was your diagnosis of the problem? My diagnosis was that Bundler copies `BUNDLE_GEMFILE` environment variable to `BUNDLE_ORIG_GEMFILE` and always uses `.bundle/config`. Simplest solution was to add parity to `bundle update` rather than diagnose why environment variables don't override `.bundle/config` settings across the board. ### What is your fix for the problem, implemented in this PR? My fix is to add the `--gemfile` option to `bundle update` for parity with `bundle install`. ### Why did you choose this fix out of the possible options? I chose this fix because this allows installing and updating alternative Gemfiles without untangling environment variables. It's the most direct use case that I'm having this issue with. Ideally, the environment variables specified for a command should be respected and override settings in `.bundle/config` (https://github.com/bundler/bundler/issues/6270).
| * Added `--gemfile` option to `bundle update`Joel Van Horn2018-01-241-0/+2
| |
* | Auto merge of #6238 - bundler:seg-outdated-fips, r=olleolleolleThe Bundler Bot2018-01-131-0/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [CLI] Skip the outdated bundler check when MD5 is not available ### What was the end-user problem that led to this PR? The problem was Bundler would try to do the outdated version check on FIPS systems, leading to an exception. Closes #6032. ### What was your diagnosis of the problem? My diagnosis was we needed to skip the check when MD5 is unavailable. ### Why did you choose this fix out of the possible options? I chose this fix because using `#available?` would make network requests, which is not acceptable.
| * | [CLI] Skip the outdated bundler check when MD5 is not availableseg-outdated-fipsSamuel Giddins2017-12-301-0/+2
| | |
* | | add `--paths` option to `bundle list` command.Colby Swandale2017-11-191-0/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | This option mimics the `--paths` options in `bundle show` which is being removed in bundler 2. Example Usage: $ bundle list --paths /Users/c/Desktop/Projects/testapp/.bundle/ruby/2.4.0/gems/actioncable-5.1.4 /Users/c/Desktop/Projects/testapp/.bundle/ruby/2.4.0/gems/actionmailer-5.1.4 /Users/c/Desktop/Projects/testapp/.bundle/ruby/2.4.0/gems/actionpack-5.1.4 /Users/c/Desktop/Projects/testapp/.bundle/ruby/2.4.0/gems/actionview-5.1.4
* | [CLI] Switch around the --strict option for bundle outdatedseg-outdated-filter-optionsSamuel Giddins2017-09-131-2/+3
| |
* | deprecate the viz command in bundler 2colby/deprecate-viz-commandColby Swandale2017-09-061-14/+17
| |
* | [CLI] Implement config subcommandsSamuel Giddins2017-08-301-8/+2
| |
View Lorry Controller Status