change gem-project to reflect bundler's recommendations
vagrant-1.1-style plugin init
vagrant-1.1 "start_mixin" has moved
vagrant-1.1 plugin styles

Command and Config plugin classes inherit from vagrant plugin classes version 2
reworked usage of vagrant internals

in vagrant 1.1 the UI interface moved from `vm` to `env`, `vm.driver` is now `vm.provider`, `vm.channel` is now `vm.communicate` and good old VirtualBox `vm.uuid` is now more general `vm.id`
Back-port: reworked usage of vagrant internals

UI interface moved from `vm` to `env`
fix typo
reworked usages of vagrant environent

in all internal classes, pass the `vm` instead of action or command `env` and use the vm's environment for all other purposes.
reworked usage of vagrant internals

in vagrant 1.1 the UI interface moved from `vm` to `env`, `vm.driver` is now `vm.provider`, `vm.channel` is now `vm.communicate` and good old VirtualBox `vm.uuid` is now more general `vm.id`
quick fix command

- remove old tests on VM state
- correct call to vbguest internals (passing vm not env)
- correct cal to UI
vagrant 1.1 style plugin loading

inspired by AWS plugin, raise an error, when not running in a vagrant environment
no longer use ruby 1.8 backwards compatibility Strings, since vagrant 1.1 depends on ruby 1.9
merge vagrant 1.0 compats
Changelog and Readme reflect vm-compat-layer

also, Readme got a better custom installer use-case
Merge pull request #50 from dotless-de/vagrant-1.1

Vagrant 1.1 support