Mitchell Hashimoto 1ee470a551 Begin work on supporting provider-specific configuration
This works by registering a `config` with `:provider => true` with the
same name as your provider. Vagrant will then automatically configure
the provider when `config.vm.provider` is used.
2012-12-23 16:29:24 -08:00

23 lines
784 B
Ruby

require "log4r"
# We don't autoload components because if we're loading anything in the
# V2 namespace anyways, then we're going to need the Components class.
require "vagrant/plugin/v2/components"
require "vagrant/plugin/v2/errors"
module Vagrant
module Plugin
module V2
autoload :Command, "vagrant/plugin/v2/command"
autoload :Communicator, "vagrant/plugin/v2/communicator"
autoload :Config, "vagrant/plugin/v2/config"
autoload :Guest, "vagrant/plugin/v2/guest"
autoload :Host, "vagrant/plugin/v2/host"
autoload :Manager, "vagrant/plugin/v2/manager"
autoload :Plugin, "vagrant/plugin/v2/plugin"
autoload :Provider, "vagrant/plugin/v2/provider"
autoload :Provisioner, "vagrant/plugin/v2/provisioner"
end
end
end