aboutsummaryrefslogtreecommitdiffstats
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* [GitProxy] Deinit submodules if they are not requestedSamuel Giddins2016-06-241-1/+5
|
* [Definition] Add a #change_reason printed in debugSamuel Giddins2016-06-241-2/+23
|
* [SpecSet] Don't mutate the skip listSamuel Giddins2016-06-241-1/+1
| | | | This could cause definition to think bundler is being updated
* [SharedHelpers] Fix printing rubygems versionSamuel Giddins2016-06-231-1/+1
|
* [Shell] Fix #silenceSamuel Giddins2016-06-231-2/+2
|
* Add spec machinery for testing major deprecationsSamuel Giddins2016-06-231-3/+2
|
* Print the first batch of major deprecation warningsSamuel Giddins2016-06-233-1/+11
|
* Add machinery for printing major deprecationsSamuel Giddins2016-06-235-10/+44
|
* [UI] Add support for printing major deprecationsSamuel Giddins2016-06-233-0/+9
|
* [Settings] Move keys to their own line & sortSamuel Giddins2016-06-231-3/+26
| | | | Will make future diffs much easier to read
* Auto merge of #4701 - chrismo:issue-4592-gem-path-empty-string, r=segiddinsHomu2016-06-241-6/+9
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unset GEM_PATH with nil not empty string. This should fix #4592, the tests all pass, but the line of code in question goes back to 2010, so this sorta seems slightly dangerous, but it's probable the circumstances of hitting this line in conjunction with `bundle exec` is a combination that didn't exist prior to 1.12.x. Issue #4592 has a full diagnosis, but the gist of it is this: if an empty string is passed as the `GEM_PATH` to the subsequent process launched by `bundle exec`, then if the `cmd` portion of `bundle exec` is a ruby shebanged file, then if the current bundle install uses a local path (`disable_shared_gems` is true) then it won't be able to find the bundler gem at all because Bundler doesn't install itself into its own Bundle, it's only installed in the system gems for the Ruby. `nil` must be passed because the RubyGems code that sets up the `GEM_PATH` does a conditional on the current `GEM_PATH` and empty string evaluates to true, whereas `nil` evaluates to false. In the false case the `GEM_PATH` is internally populated with the system gems path such that the bundler gem can be found.
| * Unset `GEM_PATH` with `nil` not empty string.chrismo2016-06-221-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This should fix #4592, the tests all pass, but the line of code in question goes back to 2010, so this sorta seems slightly dangerous, but it's probable the circumstances of hitting this line in conjunction with `bundle exec` is a combination that didn't exist prior to 1.12.x. Issue #4592 has a full diagnosis, but the gist of it is this: if an empty string is passed as the `GEM_PATH` to the subsequent process launched by `bundle exec`, then if the `cmd` portion of `bundle exec` is a ruby shebanged file, then if the current bundle install uses a local path (`disable_shared_gems` is true) then it won't be able to find the bundler gem at all because Bundler doesn't install itself into its own Bundle, it's only installed in the system gems for the Ruby. `nil` must be passed because the RubyGems code that sets up the `GEM_PATH` does a conditional on the current `GEM_PATH` and empty string evaluates to true, whereas `nil` evaluates to false. In the false case the `GEM_PATH` is internally populated with the system gems path such that the bundler gem can be found.
* | [LockfileParser] Support for old RG on Ruby 2.3+Samuel Giddins2016-06-221-4/+6
| |
* | [PostItTrampoline] Support for running as a default specSamuel Giddins2016-06-211-2/+5
| |
* | Version 1.13.0.pre.1 with changelogSamuel Giddins2016-06-201-1/+1
| |
* | Merge pull request #4671 from bundler/seg-molinillo-0.5.0Samuel Giddins2016-06-1915-200/+763
|\ \ | | | | | | Update vendored Molinillo to 0.5.0
| * | [Resolver] Mark molinillo methods as publicSamuel Giddins2016-06-191-2/+2
| | |
| * | Update vendored Molinillo to 0.5.0Samuel Giddins2016-06-1414-198/+761
| | |
* | | Merge pull request #4456 from sandlerr/sandlerr/safe_outputSamuel Giddins2016-06-193-2/+10
|\ \ \ | | | | | | | | do not log the credentials used to contact a gem server
| * | | Do not log the credentials used to contact a gem serverRoman Sandler2016-06-183-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds a filter_uri method to HTTPError backed by the URICredentialsFilter to be used when preparing error output. In the tests, replace a double object with a real URI and change a test hostname to be valid so that older versions of Ruby's URI module don't choke on it. It would be cool to somehow replace this work with the `anonymized_uri` in the Bundler::Source::Rubygems::Remote class.
* | | | Don't include dev dependencies when comparing indexes.Joe Rafaniello2016-06-171-1/+7
| | | |
* | | | Detect changes in path specs by comparing locked specs to source specsJoe Rafaniello2016-06-171-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, we'd wrongly conclude there are no path changes when there are changes. We'd parse the Gemfile.lock and compare the source.specs, the gemspecs currently in the path, to what's in the Gemfile.lock's locked.specs. Unfortunately, locked.specs for Path sources creates an Index with the specs from the filesystem and NOT what we already parsed from the Gemfile.lock! In other words, we compare the filesystems specs for a path to itself and always conclude "No changes detected!" Instead, we build an index with specs for the source we want from the already parsed Gemfile.lock. We use this index to compare to the current source.specs index from the filesystem. Ironically, this issue was masked by the bug from our prior fix, namely that dependencies_for_source_changed? always would conclude that there were changes. Because of that bug, it would short circuit out of the nothing_changed? method and force a re-resolve with path gems, which would properly build the Gemfile.lock from the prior parsed one. Undo some test changes needed to get the first fix to pass.
* | | | Use Set equality for path gems to avoid unneeded re-resolution.Joe Rafaniello2016-06-172-2/+4
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - For comparing source dependencies to locked source dependencies - For comparing two Bundler::Index dependencies Added test case. Fixed bad tests cases hidden by the above bug: - 'foo' depended on rack but we didn't build 'rack' in the path - We couldn't find 'bar' built into 'foo/bar' because the :path only had 'foo'
* / / [RubygemsIntegration] Allow redefining private methodsSamuel Giddins2016-06-141-2/+8
|/ /
* | Auto merge of #4643 - bundler:seg-postit-trampoline, r=indirectHomu2016-06-1111-1/+182
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [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
| * | [PostIt] Update for support for RubyGems 1.3.6Samuel Giddins2016-06-101-3/+3
| | |
| * | [PostIt] Update to add legacy RubyGems supportSamuel Giddins2016-06-101-2/+13
| | |
| * | Update PostIt to rescue an error that exists on old RGVsSamuel Giddins2016-06-101-1/+1
| | |
| * | Fail gracefully when installing bundler failsSamuel Giddins2016-06-101-2/+10
| | |
| * | Add total bundler version trampolining via vendored postitSamuel Giddins2016-06-1011-1/+163
| | |
* | | Auto merge of #4608 - asutoshpalai:plugin, r=segiddinsHomu2016-06-1121-95/+755
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Plugin system This is the working PR for plugin system for bundler. A rough workflow shall be - [x] Add functionality to install a plugin as gem from RubyGem source and also from git source - [x] Add support for command line plugin - [ ] Add support for source plugin - [ ] Add support for life cycle hooks - [ ] Finalize all the functionalities
| * | | Included plugins in bool_keys for settingsAsutosh Palai2016-06-104-5/+5
| | | |
| * | | Using Bundler.settings to enable plugin cliAsutosh Palai2016-06-104-6/+8
| | | |
| * | | Shifted Settings to use the YAMLSerializerAsutosh Palai2016-06-092-21/+13
| | | |
| * | | Fixed the errors in spec for older versionsAsutosh Palai2016-06-092-10/+2
| | | |
| * | | Added plugin install support for inline GemfileAsutosh Palai2016-06-094-4/+23
| | | |
| * | | Defaulting to Gem.sources for cli installAsutosh Palai2016-06-091-8/+7
| | | |
| * | | Fixed api#tmp to accept multiple namesAsutosh Palai2016-06-091-3/+3
| | | |
| * | | Made yaml_serializer compatible for use with settingsAsutosh Palai2016-06-091-2/+23
| | | |
| * | | Moved the yaml serializer to seperate moduleAsutosh Palai2016-06-092-36/+50
| | | |
| * | | Fixing Hash#select for 1.8.7Asutosh Palai2016-06-082-3/+3
| | | |
| * | | Fixes for failing specs for older ruby versionAsutosh Palai2016-06-083-5/+6
| | | |
| * | | Switching back to env to enable plugin cliAsutosh Palai2016-06-071-1/+1
| | | | | | | | | | | | | | | | | | | | The Bundler.settings is not properly initialized at that stage which lead some specs to fail
| * | | Merge branch 'master' into pluginAsutosh Palai2016-06-0722-116/+174
| |\ \ \
| * | | | Added spec for multiple plugin installAsutosh Palai2016-06-071-3/+3
| | | | |
| * | | | Multiple plugins to be installed by cli installAsutosh Palai2016-06-074-47/+49
| | | | |
| * | | | Minor correctionsAsutosh Palai2016-06-074-5/+5
| | | | |
| * | | | Using module_function in Plugin moduleAsutosh Palai2016-06-071-99/+101
| | | | |
| * | | | Added more unit specsAsutosh Palai2016-06-071-2/+2
| | | | |
| * | | | Added unit test form plugin moduleAsutosh Palai2016-06-071-2/+6
| | | | |
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-07 01:02:21 +0000