70bdd9f56e
Move host base class to a plugin component
2012-06-27 09:26:03 -07:00
53d8c28c8e
Move guests to Vagrant.plugin("1", :guest)
2012-06-26 16:28:49 -07:00
b23dda54b8
Move command base class to a plugin component
2012-06-26 16:18:02 -07:00
7258daf535
Support specifying a component for Vagrant.plugin
...
The future of subclassing things like configuration bases and so on will
be to use `Vagrant.plugin(version, component)`. For example:
`Vagrant.plugin("1", :provisioner)`.
2012-06-26 15:47:26 -07:00
ffab8cab68
Renamespace V1 plugin root to Vagrant::Plugin::V1::Plugin
...
This is mostly a transparent change to end users, but I'm going to put
all base classes for V1 into Vagrant::Plugin::V1.
2012-06-24 14:24:52 -07:00
bc0643613a
Vagrant.require_plugin [GH-916]
2012-05-06 14:01:10 -07:00
1489854d70
Move commands into plugins
2012-04-19 13:59:48 -07:00
661f20bb91
Move hosts to a plugin system
2012-04-18 22:20:45 -07:00
1cbac3167f
Move provisioners into plugins
2012-04-18 21:53:19 -07:00
1b2fa748f9
Move all guests to plugins, even the distros
2012-04-18 21:23:25 -07:00
dd459170dd
Start moving guest configuration out into plugins
2012-04-18 17:38:20 -07:00
2eebc2cb68
Basic Plugin class
2012-04-15 15:34:44 -05:00
43cadfe830
`vagrant up`
2011-12-17 09:14:05 -08:00
eda286b476
Config classes are registered via a registry now
2011-12-15 20:32:33 -08:00
b428072bb5
Provisioners use the registry. Cleaned up the way config classes are searched for.
2011-12-14 22:43:45 -08:00
Mitchell Hashimoto