8512d57076
commands/box/list: doesn't trigger Vagrantfile loading
2014-04-18 20:46:44 -07:00
1213b87679
core: vagrant help no longer loads Vagrantfile
2014-03-13 08:54:30 -07:00
998b30985f
Error message if tampering with plugins.json
2014-03-12 20:42:05 -07:00
bc31abe125
More wording changes on version conflicts
2014-03-09 22:47:56 -07:00
c391d2d46b
Don't splat the bundler groups
2014-03-09 22:41:51 -07:00
641bfd0ee6
Clarify versionconflict error
2014-03-09 22:41:23 -07:00
ba52c31bbf
core: rescue version conflicts when setting up Bundler
2014-03-05 13:16:46 -08:00
ac9e6b2078
core: error-exit machine readable output type for errors [GH-2999]
2014-02-23 22:40:45 -08:00
24a03de8bf
core: Only load default and plugin Bundler groups to avoid dev deps
2014-01-31 16:42:53 +01:00
afbed7e816
core: add output/detail methods to Ui, prefix with arrows
2014-01-17 21:02:57 -08:00
06123f9fc8
core: cleaner output when running outside installer
2014-01-17 10:39:36 -08:00
b9e701f853
catch errors that happen before Vagrant is even loaded
2014-01-08 20:04:48 -08:00
7c995caae5
core: Catch plugin load errors and show them to the user ina friendly way
2014-01-08 14:45:43 -08:00
36f64db874
Always setup plugins, but just don't always require them
2014-01-05 16:49:25 -08:00
f7e4c4df6b
setup the Bundler path always
2014-01-05 16:43:59 -08:00
8861510520
Lower some branching logic
2014-01-05 16:17:39 -08:00
73c71dbcc6
Work some things around so that Bundler is not setup with no plugins
2014-01-05 16:16:04 -08:00
76de267d1e
Don't load plugins again on `vagrant plugin` commands
2014-01-05 16:04:53 -08:00
8cfa24143d
Put plugins in their own Gemfile group so we can load on their own
2014-01-05 15:57:10 -08:00
e800743d06
fast-path vagrant --version
2014-01-05 15:32:19 -08:00
817f7f326e
fast path Vagrant --version
2014-01-05 15:27:03 -08:00
91751f6e41
load with bundler context
2014-01-05 15:26:44 -08:00
8adef9c15f
warn if running in a bundler env, don't load plugins
2014-01-04 16:29:22 -08:00
56175b8132
Replace `exit 1` with `abort`
...
According to the documentation, Kernel.abort calls Kernel.exit(false). The failure status 1 is an implementation detail on Unix-like systems. In theory, a future system could exist where 1 indicates a successful exit and 0 indicates a failure.
2014-01-03 17:32:45 +01:00
3219be3d51
core: only look for global flags before "--" [GH-2491]
2013-11-25 11:42:06 -08:00
f861fbcafb
Update CHANGELOG
2013-11-24 11:58:06 -08:00
0c19578afa
Merge pull request #2261 from mrkafk/master
...
core: check ENV for VAGRANT_NOCOLOR (equivalent of --no-color on cmdline)
2013-11-24 11:57:16 -08:00
42a71a953d
commands/status: add machine-readable output
2013-11-24 11:11:38 -08:00
c5a7ab7953
core: Add the MachineReadable UI, --machine-readable flag
2013-11-24 11:04:54 -08:00
de9d38de21
core: don't load vagrantfile on plugin command
2013-11-23 13:25:33 -08:00
28740943bb
Add `--debug` option as a shortcut for `VAGRANT_LOG=debug`
...
When asking or submitting debug information, a command line switch is
easier and faster than using an environment variable.
2013-10-31 22:20:13 -03:00
eb6256316c
core: improved commenting in bin/vagrant
2013-10-23 23:20:27 -07:00
e4b6c91b7c
check ENV for VAGRANT_NOCOLOR (equivalent of --no-color on cmdline)
2013-09-23 19:21:51 +02:00
f65f2d20d9
Remove 'v' prefix on version number in vagrant -v
2013-09-06 11:14:17 -07:00
896ae7b9ba
core: vagrant -v no longer loads Vagrantfile
2013-09-02 15:43:59 -07:00
7c9219fc18
Add --color to force color output [GH-2027]
2013-08-09 11:40:08 -07:00
5ca89383f8
Simplify cygwin check everywhere
2013-04-06 16:05:13 -07:00
fb9c311b4d
Always colorize Cygwin output
2013-04-06 16:03:25 -07:00
b32c0d16ac
Better plugin dev experience through warnings
2013-03-28 17:10:07 -07:00
9c7bedfb63
Always unload the environment
2013-03-03 00:09:40 -08:00
2b37185994
Don't load plugins when using the `vagrant plugin` interface
2013-02-28 22:32:13 -08:00
46db50680b
environment_unload hook
2013-02-22 13:54:28 -08:00
0d27cd5bcb
Warn if Vagrant is run outside of installers
2013-01-28 13:39:56 -08:00
a50539bc78
Remove the development version warning
2013-01-28 12:44:24 -08:00
a4713d5a84
No need to call `load!` anymore, since it doesn't exist
2012-12-23 16:29:23 -08:00
de73b65635
Very early SIGINTs no longer cause ugly stack traces.
...
We catch INT very very early in the Vagrant process in order to exit
cleanly rather than raising any exceptions. This is eventually overriden
by Vagrant at some point.
2012-08-10 00:30:58 -07:00
d6249f671d
folder is ~/.vagrant.d not ~/vagrant.d
2012-07-26 10:57:20 -04:00
141dccd4e7
Modify warning message to be more clear [GH-1027]
2012-07-16 09:49:04 -07:00
c634cbedcc
Handle interrupts more gracefully on the warning message
2012-07-11 18:47:41 -07:00
933b0b3101
Clarify that the warning will be removed when official version is
...
released
2012-07-11 18:34:36 -07:00
Mitchell Hashimoto
Erik Michaels-Ober
Teemu Matilainen
root
Greg Poirier
Sean Coates