bundler-inject 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 834b4bd13923ff8caf120998b70f6c4e1daa653892846b6e6fc20fbd614f8963
+  data.tar.gz: faa0f483d05511d3bfdac39a87c4cb0f9a8b2ac3b3a3fe02c650c013090f4acb
+SHA512:
+  metadata.gz: a39735242f3323779362935234af1dbeac7eba4b307a0b4f9a497139a3cd06a07cb03d9e52202e72f25a535b51b3b61c34de5d2bf121ea15ec24e628b40f746b
+  data.tar.gz: 89411f99b21e2b814e36818cee44dd7e5f359080607d497c647789e8208bb76c059d82af5bfb0b8223166dc4be4badf60e0bd3def1b795e974f8f7dd76bdaca2

data/.codeclimate.yml

@@ -0,0 +1,30 @@
+---
+version: '2'
+prepare:
+  fetch:
+  - url: https://raw.githubusercontent.com/ManageIQ/guides/master/.rubocop_base.yml
+    path: ".rubocop_base.yml"
+  - url: https://raw.githubusercontent.com/ManageIQ/guides/master/.rubocop_cc_base.yml
+    path: ".rubocop_cc_base.yml"
+checks:
+  argument-count:
+    enabled: false
+  complex-logic:
+    enabled: false
+  file-lines:
+    enabled: false
+  method-complexity:
+    config:
+      threshold: 11
+  method-count:
+    enabled: false
+  method-lines:
+    enabled: false
+  nested-control-flow:
+    enabled: false
+  return-statements:
+    enabled: false
+plugins:
+  rubocop:
+    enabled: true
+    config: ".rubocop_cc.yml"

data/.gitignore

@@ -0,0 +1,12 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/Gemfile.lock
+
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,4 @@
+--format documentation
+--color
+--require spec_helper
+--order random

data/.rubocop.yml

@@ -0,0 +1,3 @@
+inherit_from:
+- https://raw.githubusercontent.com/ManageIQ/guides/master/.rubocop_base.yml
+- .rubocop_local.yml

data/.rubocop_cc.yml

@@ -0,0 +1,4 @@
+inherit_from:
+- .rubocop_base.yml
+- .rubocop_cc_base.yml
+- .rubocop_local.yml

data/.travis.yml

@@ -0,0 +1,21 @@
+---
+language: ruby
+cache: bundler
+rvm:
+- 2.4.5
+- 2.5.3
+env:
+- TEST_BUNDLER_VERSION=1.15
+- TEST_BUNDLER_VERSION=1.16
+- TEST_BUNDLER_VERSION=1.17
+- TEST_BUNDLER_VERSION=2.0
+before_install:
+- 'echo ''gem: --no-ri --no-rdoc --no-document'' > ~/.gemrc'
+- gem install bundler -v "~> $TEST_BUNDLER_VERSION.0"
+before_script:
+- curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64
+  > ./cc-test-reporter
+- chmod +x ./cc-test-reporter
+- "./cc-test-reporter before-build"
+after_script:
+- "./cc-test-reporter after-build --exit-code $TRAVIS_TEST_RESULT"

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in bundler-inject.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -0,0 +1,151 @@
+# bundler-inject
+
+[![Build Status](https://travis-ci.org/ManageIQ/bundler-inject.svg?branch=master)](https://travis-ci.org/ManageIQ/bundler-inject)
+[![Maintainability](https://api.codeclimate.com/v1/badges/e4650d6dd7cbcd981057/maintainability)](https://codeclimate.com/github/ManageIQ/bundler-inject/maintainability)
+[![Test Coverage](https://api.codeclimate.com/v1/badges/e4650d6dd7cbcd981057/test_coverage)](https://codeclimate.com/github/ManageIQ/bundler-inject/test_coverage)
+[![Security](https://hakiri.io/github/ManageIQ/bundler-inject/master.svg)](https://hakiri.io/github/ManageIQ/bundler-inject/master)
+
+**bundler-inject** is a [bundler plugin](https://bundler.io/guides/bundler_plugins.html)
+that allows a developer to extend a project with their own personal gems and/or
+override existing gems, without having to modify the Gemfile, thus avoiding
+accidental modification of git history.
+
+## Installation
+
+Add these lines to your application's `Gemfile`:
+
+```ruby
+plugin 'bundler-inject'
+require File.join(Bundler::Plugin.index.load_paths("bundler-inject")[0], "bundler-inject") rescue nil
+```
+
+Additionally, commit a `bundler.d/.gitkeep` file, and add `/bundler.d` to your
+`.gitignore` file. This will be one of the locations developers can place their
+overrides.
+
+## Usage
+
+Once the above lines are in the Gemfile, subsequent bundle commands will attempt
+to evaluate extra gemfiles from two locations if they are present.
+
+- global - `~/.bundler.d/*.rb`
+- project - `$PROJECT_DIR/bundler.d/*.rb`
+
+For example, a developer may prefer the `pry` gem over `irb`, but can't use it
+because the project Gemfile doesn't have `pry` in it. Instead of modifying the
+Gemfile and hoping they don't commit the changes, they can create a
+`bundler.d/developer.rb` file with the contents set to `gem "pry"`. From then on
+the developer can use `pry`, even though the project didn't state it explicitly.
+
+Since this example developer likely *always* wants to use `pry`, it would be
+preferable to specify this as a global choice in a `~/.bundler.d/developer.rb`
+file instead.
+
+### override_gem
+
+`override_gem` is an extra DSL command that allows overriding existing gems from
+the Gemfile. A useful example of this is if you are making a change to a
+dependent gem, and temporarily want to override the existing `gem` definition
+with, a git or path reference.
+
+For example, there is a project with a Gemfile with `gem "foo"` in it. We want
+to fix a bug in foo, and we intend to make a pull request to upstream, but in
+the interim we want to test our foo change with the project. Instead of
+modifying the Gemfile and hoping we don't commit the changes, we can create a
+`bundler.d/developer.rb` with the contents set to
+`override_gem "foo", :git => "https://github.com/me/foo.git"`. bundler-inject
+will output a warning to the screen to make us aware we are overriding, and
+then it will use the new definition.
+
+`override_gem` will raise an exception if the specified gem does not exist in
+the original Gemfile.
+
+### ensure_gem
+
+`ensure_gem` is an extra DSL command similar to `override_gem`, and primarily
+meant for the global override file.
+
+One issue with the global file is that it specifies a new gem with `gem`, but
+that gem already exists in the project you will get a nasty warning. Conversely,
+if it specifies an override with `override_gem`, but the gem does not exist in
+the project you will get an exception. To deal with these issues, you can use
+`ensure_gem` in your global file.
+
+`ensure_gem` works by checking if the gem is already in the dependency list, and
+comparing the options specified. If the dependency does not exist, it uses `gem`,
+otherwise if the options or version specified are significantly different, it
+will use `override_gem`, otherwise it will just do nothing, deferring to the
+original declaration.
+
+## What is this sorcery?
+
+While this is technically a bundler plugin, bundler-inject does not use the
+expected plugin hooks/sources/commands. To understand how this works and why
+these were not used, it's useful to understand how bundler passes over your
+Gemfile.
+
+For `bundle install`/`bundle update`, bundler makes two passes over the Gemfile.
+
+On the first pass, bundler executes your Gemfile in a `Bundler::Plugin::DSL`
+context. This class is a special subclass of `Bundler::Dsl`, where nearly all of
+the usual DSL methods like `gem` and `gemspec` are a no-op, and the `plugin` DSL
+method does it's thing. So, after the first pass, bundler sees only your plugin
+gems, and will then install them into `.bundle/plugin`.
+
+On the second pass, bundler executes your Gemfile in a `Bundler::Dsl` context,
+where the usual DSL methods like `gem` and `gemspec` do their thing, and the
+`plugin` DSL method is instead a no-op. This is the pass most people think of.
+
+On the very first install of the plugin, between the two passes, bundler will
+load your plugin to see what kind of features it has, whether hooks, sources, or
+commands, and will store this information in the `.bundle/plugin/index` file.
+It would seem that since the plugin code is loaded this would be an opportune
+time to do what we need, but unfortunately this only happens on initial install.
+On subsequent `bundle update` calls, bundler sees that the index file exists,
+and doesn't need to load the plugin, since all of the information is in the
+index.
+
+Complicating the matter further, for `bundle check`/`bundle exec`, bundler makes
+only one pass over the Gemfile in a `Bundler::Dsl` context.
+
+One immediate question on your mind may be, why not just define a fake hook or
+source, and then put the code in there. Unfortunately, the problem is that any
+of hooks, sources, or commands that will trigger the load of the plugin occur
+after the Gemfile has already been passed over, preventing us from adding to the
+DSL, as well as loading extra gemfiles.
+
+As such, the earliest we can possibly trigger our plugin load in all cases is
+immediately after we declare the plugin in the Gemfile. This is why we need that
+magic line after the plugin line in the Gemfile.
+
+Once we have the ability to trigger a load of our plugin, whether direct via the
+magic line, or automatically on first plugin installation, then the plugin can
+manipulate the Bundler::Dsl to add the `override_gem` method and trigger the
+eval of extra gemfiles.
+
+## Development
+
+Development of bundler plugins can be a little strange, with a few gotchas.
+
+1. bundler installs your gem into the .bundle/plugin directory of the target
+   project.
+2. `plugin "bundler-inject", :path => "/path/to/bundler-inject"` doesn't work
+   as expected since bundler needs to "install" your gem into .bundle/plugin,
+   and thus doesn't know how. To get around this, use
+   `:git => File.expand_path("/path/to/bundler-inject")`.
+3. If you are using :git (which also applies to :path with the workaround
+   above), bundler will only consider committed code. Therefore, you *must*
+   commit your code in a temporary commit if you want it to be picked up.
+4. bundler plugins are copied to .bundle/plugin only on first install, and then
+   updated only if a change is detected. Unless you have a `:ref` or a changing
+   version number, bundler will think your gem hasn't changed and will not
+   update it, even if you commit something. To force bundler to pull in your
+   changes, you will have to `rm -rf .bundle/plugin`.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/ManageIQ/bundler-inject.
+
+## License
+
+This project is available as open source under the terms of the [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0).

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "bundler/inject"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/bundler-inject.gemspec

@@ -0,0 +1,29 @@
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "bundler/inject/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "bundler-inject"
+  spec.version       = Bundler::Inject::VERSION
+  spec.authors       = ["ManageIQ Authors"]
+
+  spec.summary       = %q{A bundler plugin that allows extension of a project with personal and overridden gems}
+  spec.description   = %q{bundler-inject is a bundler plugin that allows a developer to extend a project with their own personal gems and/or override existing gems, without having to modify the Gemfile, thus avoiding accidental modification of git history.}
+  spec.homepage      = "https://github.com/ManageIQ/bundler-inject"
+  spec.license       = "Apache-2.0"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler"
+  spec.add_development_dependency "colorize"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+  spec.add_development_dependency "simplecov"
+end

data/lib/bundler-inject.rb

@@ -0,0 +1,2 @@
+$LOAD_PATH.unshift(__dir__) unless $LOAD_PATH.include?(__dir__)
+require 'bundler/inject'

data/lib/bundler/inject.rb

@@ -0,0 +1,7 @@
+require "bundler/inject/version"
+require "bundler/inject/dsl_patch"
+
+Bundler::Dsl.prepend(Bundler::Inject::DslPatch)
+ObjectSpace.each_object(Bundler::Dsl) do |o|
+  o.singleton_class.prepend(Bundler::Inject::DslPatch)
+end

data/lib/bundler/inject/dsl_patch.rb

@@ -0,0 +1,100 @@
+module Bundler
+  module Inject
+    module DslPatch
+      def override_gem(name, *args)
+        raise "Trying to override unknown gem #{name.inspect}" unless (dependency = find_dependency(name.to_s))
+
+        calling_loc  = caller_locations.detect { |loc| !loc.path.include?("lib/bundler") }
+        calling_file = "#{calling_loc.path}:#{calling_loc.lineno}"
+
+        remove_dependencies_and_sources(dependency)
+        expand_gem_path(args, calling_file)
+        gem(name, *args).tap do
+          warn_override_gem(calling_file, name, args)
+        end
+      end
+
+      def ensure_gem(name, *args)
+        current = find_dependency(name)
+        if !current
+          gem(name, *args)
+        else
+          version, opts = extract_version_opts(args)
+          version = [">= 0"] if version.empty?
+          if opts.any? || (version != [">= 0"] && Gem::Requirement.new(version) != current.requirement)
+            override_gem(name, *args)
+          end
+        end
+      end
+
+      def to_definition(lockfile, unlock)
+        calling_loc = caller_locations(1, 1).first
+        if calling_loc.path.include?("bundler/dsl.rb") && calling_loc.base_label == "evaluate"
+          load_global_bundler_d
+
+          # @gemfiles doesn't exist on Bundler <= 1.15, and we can't get at @gemfile
+          #   by this point, but there's a high probability it's just "Gemfile",
+          #   or slightly more accurately, the lockfile name without the ".lock" bit.
+          targets = defined?(@gemfiles) ? @gemfiles : [Pathname.new(lockfile.to_s.chomp(".lock"))]
+
+          targets.reverse_each do |gemfile|
+            load_local_bundler_d(File.dirname(gemfile))
+          end
+        end
+        super
+      end
+
+      private
+
+      def find_dependency(name)
+        dependencies.find { |d| d.name == name }
+      end
+
+      def remove_dependencies_and_sources(dependency)
+        removed_dependency = dependencies.delete(dependency)
+        if removed_dependency.source.kind_of?(Bundler::Source::Git)
+          @sources.send(:source_list_for, removed_dependency.source).delete_if do |other_source|
+            removed_dependency.source == other_source
+          end
+        end
+      end
+
+      def expand_gem_path(args, calling_file)
+        return unless args.last.kind_of?(Hash) && args.last[:path]
+        args.last[:path] = File.expand_path(args.last[:path], File.dirname(calling_file))
+      end
+
+      def extract_version_opts(args)
+        args.last.is_a?(Hash) ? [args[0..-2], args[-1]] : [args, {}]
+      end
+
+      def warn_override_gem(calling_file, name, args)
+        return if ENV["RAILS_ENV"] == "production"
+
+        version, opts = extract_version_opts(args)
+        message = "** override_gem(#{name.inspect}"
+        message << ", #{version.inspect[1..-2]}" unless version.empty?
+        message << ", #{opts.inspect[1..-2]}" unless opts.empty?
+        message << ") at #{calling_file}"
+        message = "\e[33m#{message}\e[0m" if $stdout.tty?
+
+        warn message
+      end
+
+      def load_global_bundler_d
+        load_bundler_d(File.join(Dir.home, ".bundler.d"))
+      end
+
+      def load_local_bundler_d(dir)
+        load_bundler_d(File.join(dir, "bundler.d"))
+      end
+
+      def load_bundler_d(dir)
+        Dir.glob(File.join(dir, '*.rb')).sort.each do |f|
+          Bundler.ui.debug "Injecting #{f}..."
+          eval_gemfile(f)
+        end
+      end
+    end
+  end
+end

data/lib/bundler/inject/version.rb

@@ -0,0 +1,5 @@
+module Bundler
+  module Inject
+    VERSION = "1.0.0"
+  end
+end

data/plugins.rb

@@ -0,0 +1 @@
+require 'bundler-inject'

metadata

@@ -0,0 +1,135 @@
+--- !ruby/object:Gem::Specification
+name: bundler-inject
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+platform: ruby
+authors:
+- ManageIQ Authors
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2019-03-05 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: colorize
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: simplecov
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description: bundler-inject is a bundler plugin that allows a developer to extend
+  a project with their own personal gems and/or override existing gems, without having
+  to modify the Gemfile, thus avoiding accidental modification of git history.
+email: 
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".codeclimate.yml"
+- ".gitignore"
+- ".rspec"
+- ".rubocop.yml"
+- ".rubocop_cc.yml"
+- ".rubocop_local.yml"
+- ".travis.yml"
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- bundler-inject.gemspec
+- lib/bundler-inject.rb
+- lib/bundler/inject.rb
+- lib/bundler/inject/dsl_patch.rb
+- lib/bundler/inject/version.rb
+- plugins.rb
+homepage: https://github.com/ManageIQ/bundler-inject
+licenses:
+- Apache-2.0
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.7.6
+signing_key: 
+specification_version: 4
+summary: A bundler plugin that allows extension of a project with personal and overridden
+  gems
+test_files: []