Fix 'No error message' errors
Merge branch 'no-error-message' of github.com:leth/vagrant-vsphere into leth-no-error-message
Fixes another missed error in the style of leth.
Pump up the semver.
Updates clone.rb/get_name() to allow fqdn's as VM name (dot's previously not allowed)
Fixed missing resource pool in linked clone from a template
#62 - Use root resource pool when cloning from template
fixed "No error message" errors in VIM helper methods
Supports differentiating between SSH/WinRM communicator now that new Vagrant version supports Windows guests
Merge pull request #59 from marnovdm/feature/allow_fqdn_vm_name

Updates clone.rb/get_name() to allow fqdn's as VM name
Merge pull request #65 from mkuzmin/no-error-message

Incorrect configuration values cause "No error message" output
for the moment: force ruby 2.0.0 and vagrant 1.5.0 when building the gem
Merge branch 'resource-pool' of github.com:mkuzmin/vagrant-vsphere into mkuzmin-resource-pool
Merge branch 'mkuzmin-resource-pool' #61
Check if config.vm.communicator is defined before checking if it's set to WinRM - fixes unit tests
Updates unit test to add communicator field to vm_config in spec_helper.rb and fixes if defined check
Instruct vagrant to set the guest hostname according to Vagrantfile configuration
Add new configuration parameter 'vm_base_path' which adds ability to clone VM into a folder different to template location
Add vm_base_path to readme file
fixed synced folders to work with WinRM communicator