aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler/cli
Commit message (Collapse)AuthorAgeFilesLines
...
| * doctor: use Bundler::NULLMisty De Meo2016-08-021-2/+2
| |
| * doctor: gems not being installed isn't fatalMisty De Meo2016-08-021-2/+2
| |
| * doctor: return stub result if no dylib tool installedMisty De Meo2016-08-021-0/+10
| | | | | | | | | | This will eventually support other tests, so the dylib test needs to be able to to meaningfully return an empty result
| * Add command to diagnose common issuesMisty De Meo2016-08-021-0/+85
| | | | | | | | | | | | | | | | | | | | This new command, doctor, checks for common problems. Currently, it looks for broken dynamic library links in C extensions. It scans all of the specifications in the bundle for .bundle files in C extensions. If any of the dynamic libraries linked against no longer exist, bundler will report a message to the console.
* | [Binstubs] Update for Installer not inheriting from EnvironmentSamuel Giddins2016-08-031-1/+1
|/
* Return out of `warn_if_outdated` if installed ver satisfies running verBoggs2016-07-291-0/+1
|
* [RuboCop] Update to 0.41.2Samuel Giddins2016-07-202-2/+3
|
* JRuby in 1.8 mode doesn't support Array as first argument for Kernel.execojab2016-07-161-1/+5
| | | | Fixes #4586
* Add JRuby shebang to ruby_shebang? checkojab2016-07-161-0/+1
| | | | It allows commands to be executed via `.kernel_load` on JRuby
* Auto merge of #4741 - bundler:seg-1-99-rebase, r=indirectHomu2016-07-132-0/+8
|\ | | | | | | | | | | Re-integrate 1-99-dev into master @indirect please make sure I didn't miss anything here?
| * Migrate 1-99 deprecations to new major_deprecation machinerySamuel Giddins2016-07-052-6/+4
| |
| * Show deprecation warning when using console commandDimitris Zorbas2016-07-051-0/+4
| |
| * Show deprecation warning when using --binstubsStefan Lance2016-07-051-0/+6
| |
* | Raise message on multiple optionschrismo2016-07-081-2/+3
| |
* | Hook-up `--strict` option, flesh out update specs.chrismo2016-07-081-1/+4
| | | | | | | | | | Getting caught up on missing update_specs, realized `--strict` flagged wasn't being passed through. Fixed.
* | Invalid level in GemVersionPromoter now raises.chrismo2016-07-081-1/+1
| | | | | | | | | | This shouldn't ever surface to the user, would be the result of a coding mistake.
* | GemVersionPromoter refactorchrismo2016-07-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | UpdateOptions which was then renamed to DependencySearch is now called GemVersionPromoter, cuz I can't name this damn class. It's in its own file now, so there's that. I took a shot at moving Resolver#search_for into it, but had naively overlooked a few instance variables and such and it just didn't make as much sense as I'd first envisioned. Probably some other smaller classes in between perhaps. GemVersionPromoter class now caching its results, too, and I moved out the return from it back into Resolver as it made more sense there. As a standalone class, it may make sense to have this actually implement :major sorting, but maybe later.
* | Rename UpdateOptions=>DependencySearchchrismo2016-07-081-1/+1
| |
* | RuboCop fixeschrismo2016-07-081-1/+1
| |
* | minor/patch resolution code invokable.chrismo2016-07-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Prior commit added in the code but it only worked in the default :major case by staying out of the way, so it at least didn't break existing functionality. But the GemsToPatch class hadn't been brought over from bundler-patch yet, so none of the patch/minor code could work as it was referencing an ivar that didn't exist yet. Bundler-patch not only will handle an update to whatever is the latest patch/minor version, but will also handle an update to a version specified in an advisory from ruby-advisory-db. At this point I don't believe we'll be adding the advisory behavior to Bundler proper, so this commit can bring over simply the array of gem names being updated without the GemsToPatch class or the extra sorting code that takes a specific version number into account. With these simplifications, the starter update_spec can run without exception, though for some reason it's behaving as if the :minor level were specified, instead of :patch. Rather than keep debugging from an integration level, it's time to start bringing over resolver tests.
* | UpdateOptions added and passed thru all_the_thingschrismo2016-07-081-1/+3
| | | | | | | | | | | | | | | | | | | | | | First shot adding new update CLI options and passing those through Definition into Resolver where they're needed. I opted for three separate options to reduce typing, vs. a --level [patch|minor|major]. It's a little painful merely extending parameter lists in places, but bigger refactorings prolly be more painful.
* | Starter update_specschrismo2016-07-081-1/+1
|/
* Auto merge of #4674 - asutoshpalai:plugin, r=segiddinsHomu2016-07-051-0/+2
|\ | | | | | | | | | | [Plugin] Source plugins Adds source plugin. This is in continuation of #4608.
| * Added spec for unlockingAsutosh Palai2016-07-031-0/+2
| |
* | Auto merge of #4632 - b-ggs:bundle-add, r=RochesterinNYCHomu2016-07-041-6/+24
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add `bundle add` command to add gems into the Gemfile Continuing the work done to implement `bundle add GEM` from bundler/bundler#4546 To do: - [x] Cherry-pick commit from @ognevsky - [x] Run specs - [x] Use Bundler.definition to resolve `last_version_number` - [x] Pattern `bundle add` implementation after `bundle inject` - [x] Add option to specify added gem's `group` - [x] Add option to specify added gem's `source` - [x] Modify existing specs & add additional specs @RochesterinNYC --- Closes #4546
| * | Modify prerelease checkingBoggs2016-06-291-3/+1
| | | | | | | | | | | | Add additional specs for `--pre` flag
| * | Fix prerelease version pickingBoggs2016-06-291-1/+3
| | | | | | | | | | | | | | | | | | Add aliases for method options Rename flag for timestamp
| * | Rename flag to `--group`Boggs2016-06-271-8/+7
| | | | | | | | | | | | | | | Remove pry Fix rubocop offenses
| * | Implement --groups and --source flags for `bundle add`Boggs2016-06-271-1/+5
| | |
| * | WIP - groups and sourceBoggs2016-06-221-4/+6
| | |
| * | Remove extra parameter specifying command.Boggs2016-06-201-5/+2
| | | | | | | | | | | | | | | Change option name to `append-timestamp`, and made option checking more readable
| * | Add option to `remove_timestamp` from `Injector` class.Boggs2016-06-161-3/+5
| | |
| * | Add `--pre` flag to add prerelease gemsBoggs2016-06-151-1/+3
| | |
| * | Add specs for `bundle add`Boggs2016-06-151-1/+1
| | | | | | | | | | | | | | | | | | Fix useless assignment Remove useless spec
| * | Remove add class, add `last_version_number` method in `inject.rb`Boggs2016-06-152-43/+13
| | |
| * | Pattern bundle add implementation after bundle injectBoggs2016-06-131-17/+17
| | |
| * | Use Bundler.definition to fetch last version numberBoggs2016-06-131-6/+12
| | |
| * | Rename Adder to Add, move add to CLI namespaceBoggs2016-06-131-0/+36
| | |
* | | Auto merge of #4720 - b-ggs:4707-outdated-warning, r=RochesterinNYCHomu2016-07-041-0/+15
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Print an outdated warning when a project is locked to an old version of Bundler @indirect @RochesterinNYC I'm a bit stumped. The original issue on bundler/bundler#4707 mentions that this warning should only be printed once unless the user updates their version of Bundler, and that the warned version should be stored in `Bundler.settings[:warned_version]`. The issue is that, AFAIK, this file, `postit_trampoline.rb` is the last place where I can access both the `installed_version` (system version) and the `running_version` (project's version) of Bundler before it completely switches over to the `running_version`. Since `Bundler.settings` still hasn't been initialized at this point, I can't store the `running_version` in `Bundler.settings[:warned_version]`. Right now, this warning is shown every time a `bundle` command is issued in a project directory where `installed_version != running_version`. Is there any other way I can store the warned version from this file? --- Closes #4707
| * | Use `Bundler::VERSION` for specBoggs2016-06-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Add TODO to change to warn in 2.0 `dup` string for old rgv `dup` string for old rgv
| * | Add warnings for different versions of bundler; add specsBoggs2016-06-281-0/+15
| | | | | | | | | | | | Remove space
* | | Fixing the reserved signals and hash valueAsutosh Palai2016-06-271-1/+4
| | |
* | | Wiping all possible signalsAsutosh Palai2016-06-271-1/+1
| | |
* | | Fixes #4568Asutosh Palai2016-06-271-0/+1
|/ /
* / Don't incorrectly relativize sibling `--path` with the same prefixJon Jensen2016-06-241-1/+1
|/ | | | | | | | | | | Given current working directory `/foo/app`, when you install with `--path /foo/app_cache`, ensure that the messaging says: Bundled gems are installed into /foo/app_cache instead of the incorrect: Bundled gems are installed into ._cache
* Auto merge of #4643 - bundler:seg-postit-trampoline, r=indirectHomu2016-06-111-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | [bundle] Automatically trampoline to postit - [x] Specs ~~Except on bundle exec, since that would be too slow~~ ~~If you want, I guess we could vendor postit and manually setup the `LOAD_PATH` and `-r` the full path to the vendored postit exe. Your call.~~ Done this \c @indirect
| * Add total bundler version trampolining via vendored postitSamuel Giddins2016-06-101-1/+1
| |
* | Included plugins in bool_keys for settingsAsutosh Palai2016-06-101-1/+1
| |
* | Using Bundler.settings to enable plugin cliAsutosh Palai2016-06-101-2/+2
| |
* | Merge branch 'master' into pluginAsutosh Palai2016-06-072-0/+7
|\|
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-08 15:04:13 +0000