From b1e8506ab0568025d0510e1232cccfe8d78bd3dc Mon Sep 17 00:00:00 2001 From: Rob Eden Date: Wed, 4 May 2016 14:08:35 -0400 Subject: [PATCH] Replaces Bundler details with Wiki link --- .../docs/plugins/development-basics.html.md | 17 +++-------------- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/website/source/docs/plugins/development-basics.html.md b/website/source/docs/plugins/development-basics.html.md index 05887485a..9de36d132 100644 --- a/website/source/docs/plugins/development-basics.html.md +++ b/website/source/docs/plugins/development-basics.html.md @@ -67,20 +67,9 @@ your plugin works with another plugin. With this structure in place, your workflow should be like any other Ruby project, with one exception. Because Vagrant uses the internal -APIs of Bundler, the version of Bundler used for Vagrant development -is pinned to a specific range defined in the -[vagrant.gemspec](https://github.com/mitchellh/vagrant/blob/master/vagrant.gemspec) -file. If the upper bound version is `1.10.6`, then install the -required version of Bundler and Vagrant dependencies with the -following commands: - -``` -gem install bundler --version '1.10.6' && \ -bundle _1.10.6_ install -``` - -*Be sure to check [vagrant.gemspec](https://github.com/mitchellh/vagrant/blob/master/vagrant.gemspec) -and use the upper bound version of Bundler* +APIs of Bundler, see [Installing Vagrant from Source](https://github.com/mitchellh/vagrant/wiki/Installing-Vagrant-from-Source) +for tips for using the correct version of Bundler to install +dependencies. When you want to manually test your plugin, use `bundle exec vagrant` in order to run Vagrant with your plugin